> For the complete documentation index, see [llms.txt](https://docs.codpeller.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codpeller.com/en/subcategory-preview/obzor/functionality.md).

# Functionality

## **Subcategory Display Settings**

The app allows you to configure subcategory display **separately for the Instant Site and the Storefront**. It features **two independent blocks** for individual customization.

### Menu Butto&#x6E;**:**

* Button color in closed and open states (normal and hover)
* Button width, line thickness, and border radius

### Subcategory Lis&#x74;**:**

* Background color
* Border thickness and color
* Padding inside the category block and between subcategory elements
* Display style: **list, 2-column grid, or 3-column grid**

### Subcategorie&#x73;**:**

* Border thickness, border color, shadow, and background color
* Text color, size, style, and boldness (normal and hover)
* Subcategory image width and height
* Text padding

### Scrollba&#x72;**:**

* Slider width and color
* Scroll track color

Customize the app to match your store’s branding in just a few clicks!

🔹 **Enable the "Subcategory Preview" app now and enhance your store’s functionality!** Your customers will appreciate the convenience and enjoy a better shopping experience. 🚀


---

# 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.codpeller.com/en/subcategory-preview/obzor/functionality.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.
