> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-site-builder/unit-5-text-formats-and-rich-text/untitled.md). # Text formats Some notes on text formats: * The filters in the text format setting are applied sequentially, with the output of each filter being passed onto the next filter. * Text formats should be assigned by role. Anonymous users should only have access to plain text input format, whereas trusted users can have access to *Rich text* privileges so they can add links, images, and so on. * The HTML filter only allows the following tags by default: \ \ \ \ \
\\ \ \ \ \ \ \ \ \ \ \ \ \ \ \^{\_{\ \ \ \ \ \ \ * The site administrator can add or remove HTML tags from this list in the **Filter settings** section from **Configuration** → **Content authoring** → **Text formats and editors** → **Rich text**. A more detailed explanation of Input Formats and Filters can be found here: --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-5-text-formats-and-rich-text/untitled.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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. \ \ \}}