# Templates

Templates can be used to display controls on multiple [*Pages*](/features/pages.md) without having to add those controls to each page.

Add common application features, such as menus and footers, to a template and assign the template to multiple [*Pages*](/features/pages.md).

When a Stadium page is rendered to html, the template and the page are merged together.

By default, [*Pages*](/features/pages.md) in Stadium are all assigned an empty template called "DefaultTemplate".

***

{% embed url="<https://www.youtube.com/embed/ehkAEGiI2KI?autoplay=1&rel=0&vq=1080>" %}
Add a template
{% endembed %}

***

### How it works

1\. Page contains a form and a *Template* property that is set to "DefaultTemplate":\\

<figure><img src="/files/OkdX2I8HuTE2S5NdC7Dg" alt=""><figcaption></figcaption></figure>

2\. The *DefaultTemplate* contains a logo and a menu in the header, and a link in the footer:\\

<figure><img src="/files/joxvjFyCCYzKsyooQbaZ" alt=""><figcaption></figcaption></figure>

3\. When generated, the template and the page are merged:\\

<figure><img src="/files/i0QgBrNrqUYtmGV3Fv9E" alt=""><figcaption></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.stadium.software/features/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.