> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/contributing/documentation.md). # Documentation - [How to Contribute](https://docs.umbraco.com/contributing/documentation/getting-started.md): Whether you've found a broken link or want to add a new article, this guide will help you contribute to the Umbraco documentation. - [Submit a Pull Request](https://docs.umbraco.com/contributing/documentation/getting-started/pull-request.md): Learn the two different ways to submit a PR to the Umbraco Documentation. - [Submit Feedback](https://docs.umbraco.com/contributing/documentation/getting-started/issues.md): Learn how to provide feedback on the Umbraco Documentation. - [Create a New Version of an Article](https://docs.umbraco.com/contributing/documentation/getting-started/how-to-add-a-new-version.md): Learn how to create and add new material to the Umbraco Documentation, including updated material for upcoming releases. - [Review Documentation Locally](https://docs.umbraco.com/contributing/documentation/getting-started/review-docs.md): Learn how to use the review-docs skill in Claude Code to review documentation for clarity, style, and broken links before submitting a pull request. - [AI Contribution Guidelines](https://docs.umbraco.com/contributing/documentation/ai-guidelines.md): Guidelines for Umbraco employees contributing documentation using AI tools, covering disclosure, content ownership, tooling, and PR size. - [Style Guide](https://docs.umbraco.com/contributing/documentation/style-guide.md): Keep the Umbraco documentation accessible, consistent, and readable by following the style guide defined in this article. - [Markdown Conventions](https://docs.umbraco.com/contributing/documentation/style-guide/markdown-conventions.md): Learn how to use Markdown to write articles for the Umbraco Documentation. - [Code Samples](https://docs.umbraco.com/contributing/documentation/style-guide/code-samples.md): When adding code snippets to the Umbraco documentation, refer to this article for tips on how to improve the samples. - [File Names and Structure](https://docs.umbraco.com/contributing/documentation/style-guide/structure.md): Learn how to structure files and images when working with the Umbraco Documentation. --- # 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://docs.umbraco.com/contributing/documentation.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.