> For the complete documentation index, see [llms.txt](https://sitecoreuml.gitbook.io/sitecoredxg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitecoreuml.gitbook.io/sitecoredxg/about-the-generated-documentation/models.md). # Models *Models* are structural representations of your Sitecore templates, fields, folders, relationships, dependencies, diagrams and everything else that you see in the output documentation. Models can be thought of as the object representation of your architecture and documentation. The most important thing to remember about models is that everything you can see in the documentation has a model. The model holds the data for everything that you see, whereas the [*views*](/sitecoredxg/about-the-generated-documentation/views.md), are the actual, visual entity. {% hint style="info" %} *"The most important thing to remember about models is that **everything you can see in the documentation has a model**."* {% endhint %} In the SitecoreDXG-generated output documentation, you can find all of your models in the navigation tree in the left-pane of the page. This tree should be somewhat similar to the content tree for your templates in Sitecore, with a few extras, like diagrams and relationships. --- # 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://sitecoreuml.gitbook.io/sitecoredxg/about-the-generated-documentation/models.md?ask=&goal= ``` `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.