> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/utility-sections.md).

# Utility Sections

The small-but-useful sections, gathered in one place.

## Contact Form

Name, email, phone, and message fields; submissions go to your store's sender email. Settings: **Heading** ("Contact form"), heading size (Small → Extra extra large), color scheme, padding top/bottom (36/36). Usually lives on the Contact template — see [Pages](/sitesbyseth-docs/reign/pages.md#contact-page) — but you can add it to any page.

## Page

Renders the content of any admin page (**Online Store → Pages**) as a section — handy for reusing your returns policy or about text on other templates. Settings: **Page** picker, heading size, color scheme, **Full-width**, **Hide heading**, padding.

## Custom Liquid

A box that accepts Liquid/HTML — paste app embed snippets, tracking widgets, or custom markup without editing theme files. Settings: **Liquid code**, color scheme, padding top/bottom (40/52). If a snippet breaks your layout, just delete the section — nothing else is touched.

## Apps

A neutral container for **app blocks** (reviews widgets, size-chart apps, etc.). One setting: **Make section margins the same as theme** (on). Add the section, then add your app's block inside it.

## Quick order list

A wholesale-style variant table for the **product template**: every variant with a quantity box, so buyers order multiples fast.

| Setting                | What it does        | Default            |
| ---------------------- | ------------------- | ------------------ |
| Variants per page      | 5–50                | 50                 |
| Images                 | Show variant images | Off                |
| SKUs                   | Show SKU column     | Off                |
| Color scheme + padding | Wrapper             | Scheme 1 / 36 / 36 |

💡 Only useful for stores selling multiples (blanks, wholesale, team orders) — regular streetwear stores should skip it. A companion *bulk quick order list* powers the "Bulk" quick-add option in collection grids automatically.

## Size guide (standalone section)

⚠️ This wrapper exists in the section picker but currently renders **nothing** on the storefront — it's a placeholder. Use the real thing instead: the **Size guide block** on the product page ([Size calculator](/sitesbyseth-docs/reign/free-gift-tiers/size-calculator.md)).

## Internal sections

You may notice these in the code or section list — they're managed automatically and need no setup:

* **Cart icon bubble** — the item-count badge on the header cart icon
* **Cart notification button / product** — the "added to cart" popup (used when cart type = Popup notification)
* **Cart live region text** — screen-reader announcements for cart changes
* **Pickup availability** — the "Available for pickup" widget when local pickup is configured in Shopify shipping settings
* **Predictive search** — the live search-suggestions dropdown (toggle it in **Theme settings → Search behavior**)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/utility-sections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.