> 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/using-peakcommerce/ecommerce-and-payment-pages/adding-an-e-commerce-page.md).

# Create a Page

Pages are the visual surfaces your customers actually interact with — the storefront where they pick a plan, the checkout where they enter details, the payment page where they pay, and the portal where they self-serve. Building them in **Content → Pages** keeps design, copy, and metadata in one place and lets you reuse the same page across multiple journeys instead of rebuilding it each time.

<figure><img src="/files/huAgvhEArybJd1cdN1ae" alt="The visual page designer: a component palette on the left, a live canvas in the center with a page being built from blocks, and a properties inspector on the right"><figcaption><p>The page designer — drag components from the palette onto the canvas and configure each block's properties on the right.</p></figcaption></figure>

## Page types

The Pages list groups every page by type and shows its slug, tags, and status:

* **Storefront** — plan and product discovery; the entry point a buyer browses.
* **Checkout** — collects the details needed to place an order.
* **Payment** — captures a payment method or pays an invoice (see [External & Hosted Payment Pages](/product/using-peakcommerce/ecommerce-and-payment-pages/external-payment-pages.md)).
* **Portal** — authenticated self-service surfaces for existing customers.

## Add a page

1. Go to **Content → Pages**.
2. Click **New Page** to start from scratch, or **From Template** to start from a prebuilt layout.
3. Give the page a **name** and choose its **type**.
4. Build the page in the editor by dragging [components](/product/using-peakcommerce/templates.md) onto the canvas and configuring each block.
5. Set the page's **SEO metadata** (title tag and meta description) so it surfaces well in search.
6. **Publish** the page. Each published page gets a public **slug** (for example `/s/signup`); the slug is unique within your tenant.

Bind a published page to a [journey step](/product/journeys-and-pages/journey-steps/managing-journey-steps.md) to use it inside a guided flow.

## Styling with brand colors

* **Heading** and **Text** blocks carry a **Color** control offering the brand palette — surface, brand, ink, and muted variants — so copy stays on-brand without hand-picking hex values.
* **Container** and **Section** background colors come from the same curated palette. Pages authored earlier with custom hex values keep rendering exactly as saved.
* The built-in **Marketing** blocks (Pricing Table, Feature Grid, Testimonial Carousel, FAQ Accordion, Plan Comparison) pick up brand colors automatically and reflow responsively on tablet and phone.

## Key concepts

* **Draft vs. published.** A page only serves publicly once published; the slug is what a journey step (or a direct link) resolves to. Edits are versioned, so you can revert a page to an earlier saved state.
* **Reuse over duplication.** Because pages are bound to steps rather than owned by one journey, the same checkout or payment page can back several journeys.

## Gotchas

* A page that isn't **Active/published** won't resolve — a journey step pointed at a draft or unpublished slug renders nothing or 404s. Publish before you wire it up.
* Slugs must be unique per tenant; reusing a slug from another page will conflict.
* To translate a page's copy per market, see [Localizing Pages](/product/using-peakcommerce/ecommerce-and-payment-pages/translating-e-commerce-pages.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 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://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages/adding-an-e-commerce-page.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.