> 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.md). # Component Library Pages in PeakCommerce are built from **components** — reusable building blocks for storefronts, checkout, payment pages, and customer / partner / CSR portals. The **Component Library** (**Content → Component Library**) is where these components live, where you create your own, and where you keep your building blocks consistent across every page and portal. Rather than hand-coding each page, you compose pages visually from components in the page editor. System components ship ready to use; user components let you standardize your own design once and reuse it everywhere. * [Working with Components](/product/using-peakcommerce/templates/templates-overview.md) — the component model: category, contexts, source, and status * [Creating a Component](/product/using-peakcommerce/templates/creating-a-component.md) — build one by hand or generate it with Mango Pages themselves — where components get placed — live under [Ecommerce & Payment Pages](/product/using-peakcommerce/ecommerce-and-payment-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/templates.md?ask=&goal= ``` `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.