> 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-engage/getting-started/for-developers.md).

# For Developers

Find information to effectively integrate and customize Umbraco Engage within your environments.

In this section, you will find essential information on system requirements, licensing details, and infrastructure considerations.

## [Infrastructure Sizing](/umbraco-engage/getting-started/for-developers/infrastructure-sizing.md)

Get insights on sizing your infrastructure to meet your project's demands.

## [Load Balancing and CM/CD Environments](/umbraco-engage/getting-started/for-developers/loadbalancing-and-cm-cd-environments.md)

Discover best practices for setting up load balancing and managing continuous integration and deployment environments.

## [Content Delivery Network (CDN) Recommendations](/umbraco-engage/getting-started/for-developers/content-delivery-network-recommendations.md)

Explore recommended CDN options to improve content delivery speeds.

## [Cockpit](/umbraco-engage/getting-started/for-developers/cockpit.md)

View with the technical aspects of the Cockpit for managing marketing features within Umbraco Engage.

## [Content Security Policy (CSP) Nonce Configuration](/umbraco-engage/getting-started/for-developers/content-security-policy-nonce-configuration.md)

Configure a nonce to be used by Engage scripts & styles for your content security policy.


---

# 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-engage/getting-started/for-developers.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.