> 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/17.latest/model-your-content/content-types-and-structure/backoffice/document-blueprints.md).

# Document Blueprints

{% hint style="info" %}
Document Blueprints were previously called Content Templates.
{% endhint %}

## Document Blueprints Overview

A Document Blueprint allows editors to preconfigure a content node. It serves as a reusable starting point when creating new content.

### Method 1 – Create a Document Blueprint from the Content Section

{% hint style="warning" %}
Before using this method, make sure you have already [created some content](/umbraco-cms/17.latest/model-your-content/content-types-and-structure/data/defining-content.md#3-creating-the-content).
{% endhint %}

1. Go to the **Content** section and select an existing content node.

![Content-Menu](/files/WIdnl3esCXohIAG8TOlM)

2. Click the **...** menu next to the node and choose **Create Document Blueprint**.

![Action Button](/files/wI0Tgigk6MSSwsdmuoHU)

3. Enter a **Name** for the new blueprint.

![Document Blueprint Name Field](/files/jHRO9qNdJVm2O4UJ6C1o)

4. Click **Save**.

The new blueprint will appear under the **Document Blueprints** folder in the **Settings** section.

![New Document Blueprint](/files/82oqmMvTqeloED8wOfMh)

{% hint style="info" %}
If you don’t see the new blueprint, try refreshing your browser.
{% endhint %}

### Method 2 – Create a Document Blueprint from the Settings Section

1. Go to the **Settings** section.
2. Click the **...** menu next to the **Document Blueprints** tree.
3. Select **Create...**.

![Create Document Blueprint](/files/Eg57OGvN9sjyP02sDpkK)

4. Choose the Document Type you want to base the blueprint on.

![Select Content Type](/files/ZhCAwUvCbGAuRAnsclIN)

{% hint style="warning" %}
You can only create Document Blueprints from **Document Types** or **Document Types with Templates**.
{% endhint %}

5. Enter a **Name** for the blueprint.
6. Click **Save**.

The new blueprint will appear under the **Document Blueprints** folder in the **Settings** section.

### Edit a Document Blueprint

To edit an existing document blueprint, follow these steps:

1. Go to the **Settings** section.
2. Open the **Document Blueprints** folder.
3. Select the blueprint you want to edit.
4. Make your changes.
5. Click **Save**.

![Edit Document Blueprint](/files/7mE3jUcvpJzedQOZEGrF)

### Use a Document Blueprint

Once you have created a document blueprint, you can use it to create new content nodes.

{% hint style="info" %}
Document Blueprints can only be selected when creating a new content node. They cannot be applied to existing content.
{% endhint %}

To use a document blueprint, follow these steps:

1. Go to the **Content** section.
2. Click the **...** menu next to the root node and select **Create**.

![Create From Template](/files/Vtj4DeouKfczWvDhR0uv)

3. Select the **Document Type** that has an associated blueprint.

![Select the Document Type](/files/mn6NwzZf0ghlPkBlLcZv)

4. Choose how to create the new content:
   * Use the Document Blueprint
   * Start with a blank node

![Select Template](/files/5Fz6y49p45Mbl3jwWn5V)


---

# 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/17.latest/model-your-content/content-types-and-structure/backoffice/document-blueprints.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.