# Templates

Templates are groups of Components that have been put togther to create a design or layout. Once a template is dropped into your page you can customise it however you like and it won't affect the original.

The Core pack inside of Elements includes a selection of useful layouts for everyday web design, including menus, hero banners, layouts, forms, and more.

{% hint style="warning" %}
Globals are similar, but very different to Templates. Templates are single use and not linked. Where's Globals remain linked and are perfect for making changes across your entire site, perfect for shared menus and footers. [Learn more about Globals here](https://docs.realmacsoftware.com/elements-docs/elements/global-templates).
{% endhint %}

{% embed url="<https://youtu.be/Z8n3WPB_AFI>" %}

### **Templates vs Globals in Elements**

**Templates** are like blueprints: a quick way to drop in a ready-made layout or design made of Components.

* As soon as you add a Template to your page, it becomes a standalone set of components, completely independent from the original template.
* No matter how much (or how little) you customise it, it’s *not* linked to the original anymore.
* Changing the original template (from a Template Pack) will *not* affect anything you’ve already added to your site.
* You’re free to modify it as much or as little as you want, once the template is dropped into your site think of it as a copy, not a link!

**Want content to stay in sync across pages?** That’s where [Globals](https://docs.realmacsoftware.com/elements-docs/elements/global-templates) come in!

* [Globals](https://docs.realmacsoftware.com/elements-docs/elements/global-templates) are like master elements: place them on multiple pages and update in one place—the change is mirrored everywhere. Perfect for headers, footers, banners, and other repeat content.
* You can even override certain aspects of a [Global](https://docs.realmacsoftware.com/elements-docs/elements/global-templates) on a single page if you want a little variation.

### Supported Components

Templates can support many types of components, including:

* Built-in Components
* Third-party Components
* Custom Components
* Globals
* Resources (as part of the components)

### How to create Templates in a Project

To create a Template, drag a collection of Components from the Editor or Node Browser into the Project Templates area.

You can right-click on a Template to re-name it, or create a new folder for organisation.

<figure><img src="https://3876014504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy6AECEVH2p4eFDicpM1%2Fuploads%2FIHzrstLwWfuEDFmhkxPs%2FCleanShot%202025-06-25%20at%209%E2%80%AF.28.54%402x.png?alt=media&#x26;token=4a4e3f37-1075-4f0c-9efd-96aae61cb6dc" alt=""><figcaption><p>Elements ships with a core set of Templates.</p></figcaption></figure>

### How to create Templates to share across Projects

To build a Template Pack that is available in all projects and distributable on the Elements Store you'll need to create a new Dev Pack. This can be done from the Addons tab in the app Settings window.

You can learn more about creating [Template Packs in the Elements Language](https://docs.realmacsoftware.com/elements-docs/elements-language/element-pack/what-is-an-element-pack) section of the manual.

<figure><img src="https://3876014504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy6AECEVH2p4eFDicpM1%2Fuploads%2FFIBL0eNguptGYN8faxe0%2FCleanShot%202025-06-25%20at%209%E2%80%AF.40.13%402x.png?alt=media&#x26;token=29699216-410c-4714-b288-ee5fbb1e40ca" alt=""><figcaption><p>Use the Create Pack button in the Addons tab in the App Settings Window.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.realmacsoftware.com/elements-docs/elements/templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.