> 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-compose/content-orchestration.md).

# Content Orchestration

- [Environments](https://docs.umbraco.com/umbraco-compose/content-orchestration/environments.md): Environments are isolated workspaces within a project that keep resources and data separate, and are managed through the Management API.
- [Collections](https://docs.umbraco.com/umbraco-compose/content-orchestration/collections.md): Collections are containers for logically grouping related content within an environment, and they define the root scope for GraphQL queries (with optional traversal via references and filters).
- [Referenced Content](https://docs.umbraco.com/umbraco-compose/content-orchestration/referenced-content.md): Referenced content allows content items to be stored independently and linked together using references.
- [Type Schemas](https://docs.umbraco.com/umbraco-compose/content-orchestration/type-schemas.md): Type schemas represent the structure of your content. They describe which properties exist on a content type, and which other types it might relate to.
- [Webhooks](https://docs.umbraco.com/umbraco-compose/content-orchestration/webhooks.md): Webhooks can be used to notify your external service when content changes in Umbraco Compose.
- [Outbound Traffic](https://docs.umbraco.com/umbraco-compose/content-orchestration/outbound-traffic.md): Umbraco Compose uses static, region-specific outbound IP addresses for features like webhooks and ingestion functions, enabling you to allow them through your firewall.


---

# 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/umbraco-compose/content-orchestration.md?ask=<question>&goal=<user_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.