> 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/templates/templates-overview.md).

# Working with Components

Components are the reusable building blocks of every PeakCommerce page. You assemble pages — storefronts, checkout, payment, and customer / partner / CSR portal pages — by placing components onto them rather than editing monolithic HTML templates. Building a library of well-defined components means a change to a shared block (say your branded product card) updates consistently wherever it's used, and non-technical authors can build on-brand pages without writing markup. Browse and manage components in **Content → Component Library**.

## What defines a component

Each component in the library has:

* **Category** — how it's grouped in the library (for example Storefront, Portal Widgets, Content, or a custom category your tenant defines). Categories are just labels for organizing the library; they don't restrict where a component can be used.
* **Contexts** — the editors (and therefore the page types) a component can be placed in: **Storefront**, **Checkout**, **Customer Portal**, **Partner Portal**, **CSR Portal**, and **Payment Pages**. A component can target one context or several.
* **Source** — **System** (built-in components that ship with PeakCommerce, such as the Product Card) or **User** (components created in your tenant).
* **Status** — whether the component is **Active** (available to place on pages) or inactive.

## Components and the page editor

Pages are composed in PeakCommerce's visual editor, where each component appears as a block you can drop in, arrange, and configure. When you build or edit a [page](https://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages.md), the page's context determines which components are offered — a Storefront page surfaces Storefront-context components, a payment page surfaces payment-context ones, and so on. System components give you a ready-made starting set; user components let you reuse your own standardized blocks.

## Things to watch

* **Context, not category, controls availability.** If a component isn't appearing on the page you're editing, check that its **Contexts** include that page's editor — not just that it's in a sensible category.
* **A component must be Active to be placed.** Inactive components stay in the library for editing but won't appear in the page editor's block list.
* **System components can't be deleted**, but you can build user components that adapt or extend them — for example a tailored product card. For tuning the built-in Product Card specifically, see [Product Card Customizations](https://docs.peakcommerce.com/product/rules-and-customizations/product-card-customizations.md).

See [Creating a Component](https://docs.peakcommerce.com/product/using-peakcommerce/templates/creating-a-component.md) to add your own.


---

# 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/using-peakcommerce/templates/templates-overview.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.
