> 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/umbraco-cms/model-your-content/content-types-and-structure.md).

# Content Types and Structure

In Umbraco, all content is defined by a type. Document Types define the fields on a page, Media Types define the properties of media items, and Member Types define user profiles. This section covers how to create and configure these content types and how to build structure through compositions and relations.

* [Backoffice](/umbraco-cms/model-your-content/content-types-and-structure/backoffice.md) - key backoffice concepts: sections, trees, Document Types, Media Types, Data Types, and Property Editors.
* [Data](/umbraco-cms/model-your-content/content-types-and-structure/data.md) - define Document Types, create Media Types, configure Data Types, and manage content in the backoffice.
* [Compositions](/umbraco-cms/model-your-content/content-types-and-structure/composing.md) - share groups of properties across multiple Document Types using compositions.
* [Relations](/umbraco-cms/model-your-content/content-types-and-structure/relations.md) - define and manage relationships between different content entities.


---

# 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://docs.umbraco.com/umbraco-cms/model-your-content/content-types-and-structure.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.