> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/readme/why-is-there-a-default-layout-in-my-cms.md).

# Why is there a default Layout in my CMS?

We highly recommend that each Display has a default Layout set so something will always show in the event that there is nothing scheduled or if there is an issue that prevents the scheduled content from showing.

## Setting a default Layout

1. Click on **Displays** from the main CMS menu
2. Use the row menu for a Display and click **Edit**
3. Scroll down and use the **Default Layout** drop down to select the Layout to use
4. Click **Save**

{% hint style="success" %}
Use the Xibo default Layout provided or create your own.
{% endhint %}

Default Layouts should be simple designs with no complex media or web content so that they serve as a placeholder in the event that nothing else is shown.

## What happens if I don't set a default Layout to my Displays?

If no default Layout is set or there is an issue with the default Layout that has been set, the splash screen will be shown on Displays.


---

# 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.xibosignage.com/kb/readme/why-is-there-a-default-layout-in-my-cms.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.