> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/maintenance-and-troubleshooting/additional-troubleshooting/dynamic-customization-for-page-specific-content-in-s-docs.md).

# dynamic customization for page specific content in s docs

We often get questions about using page numbers in templates, especially when logic like `<RENDER>` or conditional tags is involved.

It's important to know that all rendering and logic in the template are processed **before** special merge fields, like page numbers (`{{!PageNumber}}`, `{{!PageCount}}`), are created.

{% hint style="info" %}
This means page numbers cannot be used within logic or `<RENDER>` tags to control what content appears. Instead, they are finalized after the rest of the document is generated.

Keep this in mind when customizing templates that include special fields like page numbers!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sdocs.com/sdocs/maintenance-and-troubleshooting/additional-troubleshooting/dynamic-customization-for-page-specific-content-in-s-docs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.