> 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/settings/organization/component-categories.md). # Component Categories **Settings → Component Categories** manages the category list used by the [Component Library](/product/using-peakcommerce/templates.md) filter and the component editor's category picker. Categories are how your team browses and groups reusable blocks, so keeping the list tidy and well-ordered makes the library faster to navigate as it grows. ## What you can do * **Add** a new category for a kind of component you build often. * **Rename** a category — the change applies everywhere it's used. * **Remove** a category you no longer need. * **Drag to reorder** — the order here is the order shown in the Component Library filter and the editor's picker, so put the categories you use most at the top. Typical categories include Layout, Content, Payment, Portal Widgets, Marketing, Storefront, Journey, Custom, and Utility. Each row shows how many components currently use that category. ## How to use Order the list by how your team actually browses, not alphabetically — frequently used categories first. Lean on the usage count to decide what to keep: a category with zero components is a candidate to remove, while a high-count category is load-bearing and worth a clear name. Use **Reset** to revert unsaved changes back to the last saved list. ## Gotchas * Changes aren't live until you click **Save Categories** — navigating away first discards them. * Removing a category that components still use leaves those components uncategorized; rename instead of removing when items depend on it. Next: [Tags](/product/settings/organization/tags.md) for cross-cutting labels, or the [Settings overview](/product/settings/settings-overview.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/settings/organization/component-categories.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.