> 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/parent-child-relationships-in-models.md).

# Parent-Child Relationships of Models

SitecoreDXG visually displays the parent-child relationships of models in much the same way as Sitecore does in the Content Tree, by nesting child models under the parent model in the navigation pane. 

For example, in the below image note that the "Icon" template model is a child of the "Teasers" template folder model (module root), which is a child of the "Feature" template folder model (layer root). 

![The navigation pane of documentation generated by SitecoreDXG for Habitat](/files/-LOJ6DEfBYC3U-jv8PHY)


---

# 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/parent-child-relationships-in-models.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.