> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/experience-cloud/experience-components/application-shell.md).

# Application Shell

Use the Application Shell theme layout to give an Experience Cloud site a header, side panels and a bottom panel, with a left panel that becomes a drawer on phones and tablets.

## Overview

The **Application Shell** is a theme layout for Experience Cloud sites. Instead of building the frame of your site from the standard header and footer, you get one layout with a header, a left panel, a right panel and a bottom panel, around the content of each page. A typical use is an internal portal where a navigation menu stays on the left, a notifications feed sits on the right, and a status bar runs along the bottom.

You drop Avonni components into each panel in Experience Builder, for example an [**AX - Navigation**](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-navigation.md) in the left panel.

On a phone or tablet, the left panel is hidden and opens as a drawer from a button in the header, so the navigation never takes the width of a small screen.

***

## Use the Application Shell as your theme layout

1. In Experience Builder, open **Settings** and select **Theme**.
2. Create a new theme layout, or edit an existing one, and choose **Application Shell** as its component.
3. Assign that theme layout to the pages that should use it, in the page properties.
4. Select the layout in the canvas and set its properties (see below). Then add components to each region.

If saving the theme layout fails with the message "To use the selected layout, add the following required region(s)", the layout is missing its right panel and bottom panel regions. Add `rightPanelRegion` and `bottomPanelRegion` to the theme layout and save again. They have to exist even when **Show Right Panel** and **Show Bottom Panel** are off.

***

## Configuration

| Property                | Description                                                                            | Default |
| ----------------------- | -------------------------------------------------------------------------------------- | ------- |
| **Show Header**         | Shows the header region, at the top of the page.                                       | On      |
| **Show Left Panel**     | Shows the left panel.                                                                  | Off     |
| **Show Right Panel**    | Shows the right panel.                                                                 | Off     |
| **Show Bottom Panel**   | Shows the bottom panel.                                                                | Off     |
| **Left Panel Width**    | Width of the left panel, in pixels. Also the width of the drawer on a phone or tablet. | `250`   |
| **Right Panel Width**   | Width of the right panel, in pixels.                                                   | `250`   |
| **Bottom Panel Height** | Height of the bottom panel, in pixels.                                                 | `250`   |

The page content always fills the space left between the panels, and it scrolls on its own, so the header and panels stay in place.

***

## Phone and tablet layout

When a visitor opens the site on a phone or tablet and **Show Left Panel** is on, the layout changes:

* The left panel is hidden.
* A menu button appears at the start of the header.
* Selecting the button opens the left panel as a drawer over the page, with a dark backdrop behind it and a close button at the top of the drawer.

The drawer closes when the visitor selects the close button, selects the backdrop, presses Escape, or goes to another page. If **Show Left Panel** is off, no menu button appears.

The layout follows the type of device, not the width of the screen. A narrow browser window on a computer keeps the desktop layout. Below 800 pixels wide, the left and right panels stack above the page content instead of sitting beside it.

<figure><img src="https://2929066058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDL6JQuZArjJeQvX2ot4y%2Fuploads%2Ffws3ZXhHTuwgXMV5xjzE%2Fexperience-application-shell-phone-drawer.png?alt=media" alt="Phone view of a site with the left panel open as a drawer, its close button at the top and a dark backdrop beside it" width="320"><figcaption><p>On a phone, the left panel opens as a drawer</p></figcaption></figure>

***

## Tips

* To check the phone layout while you build, switch the Experience Builder preview to the **Mobile** view mode.
* Put your site navigation in the left panel. On a phone, a navigation placed there is reached through the drawer. The **Display Actions In Mobile Menu** option of the Navigation component is a separate setting for the Navigation's own mobile menu.


---

# 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.avonnicomponents.com/experience-cloud/experience-components/application-shell.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.
