> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/sequoia-theme-documentation/site-settings/site-layouts.md).

# Site Layouts

From Elementor’s *Layout Settings,* you can set the website's *Content Width, Widgets Space, Page Title Selector, Stretched Section Fitness, Default Page Layout,* and *Breakpoints*.

Let's take a closer look at each.

## Layout

Click the hamburger menu in the Widget Panel's upper left corner and select ***Site Settings > Settings > Layout*** from any Elementor page or post editor to access the layout menu.

![](https://2425882545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCl8bwZ72WkAolEEjK0qm%2Fuploads%2F2ZHckxtS94EnD1PjD5vW%2FSequoia%20-%20Layout%20Settings.png?alt=media\&token=28b3e42f-7ed7-4268-a540-41953f267688)

1. **Content Width (px)**: Configure the content area's default width.
2. **Widgets Space (px)**: Set the widget spacing.
3. **Page Title Selector**: Enter the CSS selector for your page's title if you wish to hide it.
4. **Stretched Section Fit To**: Select the parent element to which the stretched elements will fit.
5. **Default Layout**: Choose Default, Elementor Canvas, or Elementor Full Width to define the page layout for new pages.

## Breakpoints

![](https://2425882545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCl8bwZ72WkAolEEjK0qm%2Fuploads%2FtsTNTgcqtgHjyxVsNIQp%2FSequoia%20-%20Breakpoints.png?alt=media\&token=d6683a7a-998c-4c78-8813-46ca667b103f)

1. **Mobile**: Set the mobile devices breakpoint. Mobile layout will appear below this breakpoint (Default: 768px).
2. **Tablet**: Set the tablet breakpoint. Tablet layout will be visible above and below this breakpoint for mobile devices (Default: 1025px).


---

# 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.stylemixthemes.com/sequoia-theme-documentation/site-settings/site-layouts.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.