> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/reusable-content.md).

# Templates and Globals

Reuse complete layouts with Templates and linked Globals

Templates and Globals both help you reuse groups of components, but they solve different problems.

| Feature                 | Templates                           | Globals                                |
| ----------------------- | ----------------------------------- | -------------------------------------- |
| Best for                | Starting a new layout quickly       | Repeating content across several pages |
| Connection after adding | Independent copy                    | Remains linked                         |
| Later edits             | Affect only that copy               | Can update every linked instance       |
| Common examples         | Hero sections, feature grids, forms | Menus, headers, footers, announcements |

### Templates

[Templates](/elements-docs/using-elements/reusable-content/templates.md) are reusable starting points. After adding one to a page, its components become an independent layout that can be changed without affecting the original Template or other copies.

### Globals

[Globals](/elements-docs/using-elements/reusable-content/global-templates.md) remain linked wherever they are used. Update the Global once to keep shared structures and content consistent throughout the project.

{% hint style="info" %}
Use a Template when each copy should evolve independently. Use a Global when every instance should continue sharing the same source.
{% endhint %}

### Recommended Workflow

1. Build and test the component layout on a page.
2. Decide whether future copies should remain linked.
3. Save independent starting points as Templates.
4. Save site-wide or repeatedly maintained content as Globals.
5. Preview changes on every page where the layout appears.


---

# 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.realmacsoftware.com/elements-docs/using-elements/reusable-content.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.