> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-editor/built-in-elements/layout-container.md).

# Layout Container

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FmrAwTW9m33uq3lPQGjsg%2Fimage.png?alt=media&amp;token=187c763c-224e-4f71-a699-0fd99c1b7fad" alt="" width="73"><figcaption><p>Layout Container</p></figcaption></figure></div>

The **`Layout Container`** element plays an important role when it comes to designing your page. Many other built-in elements make use of the layout container and related elements like [Layout Row](/app-editor/page-editor/built-in-elements/layout-row.md) and [Layout Column](/app-editor/page-editor/built-in-elements/layout-column.md) inside them.

The layout container contains one or more layout row elements, with each row containing one or more layout column elements.

The example below shows a layout container (Container27) with two layout rows (Row26 and Row28).  The Row26 layout row has three layout columns and the Row28 layout row has two. (See the page tree view image for spotting these elements).

<div><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FiWGzEOH6YzDDw8uQ7SJo%2Fimage.png?alt=media&amp;token=40454cf9-3718-4e57-9b1c-f3369603a117" alt=""><figcaption><p>Layout Container with two rows</p></figcaption></figure> <figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FPY5dhmYrENiABQThuqtM%2Fimage.png?alt=media&amp;token=3eeec685-5ae0-4b1d-ac51-35d55b523f0a" alt="" width="286"><figcaption><p>Layout container seen in page tree view</p></figcaption></figure></div>

{% hint style="info" %}
The only element that can be added to a layout container is a [Layout Row](/app-editor/page-editor/built-in-elements/layout-row.md).
{% endhint %}

***

## Options

The [Options tab](/app-editor/page-editor/page-element-settings.md#options-tab) settings for this element are described below:

### `Width`

Controls the width of the element based on the following values:

* Fixed

  Sets the width based on that of the element the container is placed in.

  * Width < 576px : 100% width of the element the layout container is placed in.
  * Width < 768px: 540px
  * Width < 992px: 720px
  * Width < 1200px: 940px
  * Width >= 1200px: 1140px

* Full Width

  Always occupies 100% width of the element the layout container is placed in.


---

# 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.zingy.ai/app-editor/page-editor/built-in-elements/layout-container.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.