> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/pages.md).

# Pages

**Pages** are the building blocks of journeys. Each step in a journey renders a page, and pages also power storefronts and customer/partner portals. Manage them in **Content → Pages**.

{% embed url="<https://youtu.be/7OT8Ji8jswQ>" %}

## Page types

The Pages list groups pages by type:

* **Checkout** — steps in a checkout / signup flow (e.g. plan & pricing, billing).
* **Storefront** — public landing, signup, and confirmation / thank-you pages.
* **Payment** — payment-collection pages.
* **Portal** — signed-in customer, CSR, or partner portal pages.

Each page has a **slug** (its public path, for example `/s/thank-you`) and can be tagged.

## Build a page

* Click **+ New Page** to start from scratch, or **From Template** to start from a prebuilt layout.
* Pages are composed from blocks in the **Component Library** (drag-and-drop), so you control layout and content directly.
* **Heading** and **Text** blocks have a **Color** control offering the brand palette (surface, brand, ink, and muted variants), and **Container** / **Section** background colors are picked from the same curated palette — pages saved with custom hex values before the palette keep rendering exactly as authored.
* The built-in **Marketing** blocks (Pricing Table, Feature Grid, Testimonial Carousel, FAQ Accordion, Plan Comparison) pick up your brand colors automatically and reflow responsively on tablet and phone — no per-block styling needed.
* Publish a page to make it live, then bind it to a [journey step](https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/managing-journey-steps.md) to use it in a flow.


---

# 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.peakcommerce.com/product/journeys-and-pages/pages.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.
