> 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/theme-companion/sections/adding-sections.md).
# Adding sections
Add ready-made sections to any Online Store 2.0 theme and customize them in the Theme Editor.
The **Sections** module is a catalog of ready-made sections built by Staylime — new layouts and functionality your theme doesn't have out of the box. Sections work with any Online Store 2.0 theme: you add one to a theme once, and from then on it works like any other section — place it on pages and customize it in the Theme Editor.
### Browsing the catalog
Every section card shows a preview image, and the **Preview** button opens the section live on the app's demo store — so you can see it in action before adding it. Use search and the category filter to narrow the catalog, or switch between the **All**, **Free**, and **Paid** tabs.
### Adding a section to a theme
Click **Add to theme** on a section card and pick the theme — your current theme or any theme from your library. The app adds the section's files to that theme and confirms with a banner; **Customize theme** takes you straight to the Theme Editor.
Each section can be added to a theme once — if it's already there, the app tells you instead of adding a duplicate.
### Using a section in the Theme Editor
In the Theme Editor, click **Add section** — sections from Theme Companion appear at the top of the list with a **TC:** prefix (for example, *TC: Collections table*). From there it behaves like a native theme section: add it to any page and adjust its settings in the editor panel.
Sections you've added become part of the theme's files — so they carry through theme updates like the rest of your customizations.
---
# 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/theme-companion/sections/adding-sections.md?ask=&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.
