> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/sections/layout/apps.md).

# Apps

A dedicated section for placing app blocks exactly where you want them.

Most Shopify apps ship their own blocks, but a block needs a section to live in — and templates don't always offer one in the right place. The Apps section is that container: an otherwise empty section whose only job is to hold app blocks, positioned wherever you drop it.

{% hint style="info" %}
**At a glance**

| Where to find it | **Add section → Layout**                                       |
| ---------------- | -------------------------------------------------------------- |
| Holds            | App blocks only — more than one, in the order you arrange them |
| Content settings | None of its own; nothing shows until an app block is added     |
| Typical use      | Reviews, quizzes, loyalty widgets placed where you want them   |
| {% endhint %}    |                                                                |

***

### How to add

{% stepper %}
{% step %}

### Add the section

Click **Add section** and pick **Apps** from the **Layout** category. It arrives empty — that's normal.
{% endstep %}

{% step %}

### Add the app block

Use **Add block** inside the section and pick the block your installed app provides. If the app you expect isn't listed, it doesn't offer a theme app extension block.
{% endstep %}

{% step %}

### Size it

If the block looks cramped or too narrow, adjust **Grid** or **Disable grid max-width** here rather than hunting for a setting inside the app. Turn **Use theme margins** off to let it sit flush against the screen edges.
{% endstep %}

{% step %}

### Check it on mobile

App blocks are built by third parties and don't always follow the theme's responsive behavior. Look at the section on a phone before publishing.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Uninstalling the app removes its block — the Apps section stays behind, empty.** An empty Apps section renders nothing, so it's easy to leave a handful of them scattered through your templates without noticing. Delete the section when you remove the app.
{% endhint %}

{% hint style="success" icon="lightbulb" %}

### Good to know

* **The section accepts app blocks only.** It has no content settings of its own, so nothing appears until an app block is added.
* **It can hold more than one app block,** and they render in the order you arrange them.
* **Use theme margins is on by default.** Turn it off when an app block should sit flush against the screen edges rather than inside the theme's side margins.
* **Max width appears only when Grid is set to Custom.**
* **If an app block looks cramped or too narrow,** the fix is usually **Grid** or **Disable grid max-width** here rather than a setting inside the app.
  {% endhint %}

### Customization ideas

<details>

<summary><strong>Put the reviews widget where you want it</strong></summary>

Slot it between your product grid and your footer instead of accepting whatever position the app picked for you.

</details>

<details>

<summary><strong>Make an app block read as a step</strong></summary>

Give a newsletter or quiz block its own section with **Show bottom line** enabled, so it reads as a distinct step on the page rather than part of the section above.

</details>

<details>

<summary><strong>Keep related widgets aligned</strong></summary>

Place two related app blocks in a single Apps section to keep their spacing consistent, rather than giving each one its own section.

</details>

***

### Settings reference

<details>

<summary>Settings</summary>

| Setting                    | What it does                                                     |
| -------------------------- | ---------------------------------------------------------------- |
| **Use theme margins**      | On by default. Keeps app blocks inside the theme's side margins. |
| **Grid**                   | Page, Alternative, Secondary or Custom.                          |
| **Max width**              | 1040–2560 px. Visible only with Grid set to Custom.              |
| **Disable grid max-width** | Lets content stretch past the grid's maximum width.              |
| **Show bottom line**       | Draws a divider under the section.                               |
| **Top** / **Bottom**       | Section spacing, 0–2×.                                           |

</details>

### Best practices

* **Check the app block on mobile after placing it.** App blocks are built by third parties and don't always follow the theme's responsive behavior.
* **If an app offers both a theme app extension block and a script-based embed, prefer the block here** — it can be moved, reordered and removed from the editor.
* **Audit your Apps sections when you uninstall an app.** Empty containers are invisible on the storefront and accumulate quietly.

## Related

* [Custom HTML & Custom Liquid](/docs/volume-themes/sections/layout/custom-html-and-custom-liquid.md)


---

# 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://staylime.com/docs/volume-themes/sections/layout/apps.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.
