> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/shopware6/fact-finder-web-components-for-shopware-6/category-pages-and-cms.md).

# Category pages and CMS

### Overview

Build category and search pages with Shopping Experiences. The plugin provides these Commerce blocks:

* **Search Result** — `ff-record-list`, `ff-asn`, `ff-filter-cloud`, `ff-pagination`, and `ff-sortbox`.
* **Campaigns** — feedback text, advisor, redirect, and pushed products.
* **Filters** — `ff-asn` with `ff-filter-cloud`.

Use **Landing Page** layouts. Shopware requires a default Product Listing block on Category Pages, even when you use the FACT-Finder Search Result block.

### Configure elements

Each element supports a **Subscribe** setting. Set it to `false` to prevent the element from reacting to FACT-Finder responses.

For ASN and Record List elements, configure an optional ID. The CMS element ID is used when it is empty. Both support a **Dom Updated** event listener.

Set ASN **Vertical** to add the `btn-block` class and vertical alignment.

Campaign elements can render advisor, feedback, redirect, and pushed-product components. Use labels and flags to bind components to a campaign.

### Assign layouts

Assign the completed layout to the intended categories. Keep layouts focused. Reuse the same layout where possible.

### Category path field

The default navigation field is `CategoryPath`. If your FACT-Finder instance uses another field, update the parameter in `services.xml`:

```xml
<parameter key="factfinder.navigation.category_path_field_name" type="string">CategoryPath</parameter>
```

### Extend templates

Block templates live in `Resources/views/storefront/block`. Element templates live in `Resources/views/storefront/element`.

Extend them with Shopware's `sw_extends` tag.


---

# 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.fact-finder.com/shopware6/fact-finder-web-components-for-shopware-6/category-pages-and-cms.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.