> For the complete documentation index, see [llms.txt](https://halosoft.gitbook.io/bc-nimo-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://halosoft.gitbook.io/bc-nimo-documentation/home-decor/featured-categories-1.md).

# Featured Categories 1

<figure><img src="/files/bEI6Irotl9HyU6bkSKiz" alt=""><figcaption></figcaption></figure>

The Featured Categories section is a visually rich carousel component that showcases up to 5 category collections with large images, titles, descriptions, and call-to-action buttons.&#x20;

The section also includes navigation arrows and a "View All" button for easy access to your complete category collection.

### **Setting** Featured Categories 1

Go to **Storefront** -> **My Themes** -> **Customize**. <mark style="color:red;">(If your store is a new store, you may need to go to</mark> <mark style="color:red;"></mark><mark style="color:red;">**Channel Manager -> Themes -> Edit Theme**</mark><mark style="color:red;">)</mark>

In the **Theme Editor** -> Go to **Home Page / Featured Categories 1**

<figure><img src="/files/cYEOt2zBmTASh3GVdXtS" alt=""><figcaption></figcaption></figure>

**Main Section Settings**

| Setting                  | Description                                    | Example                       |
| ------------------------ | ---------------------------------------------- | ----------------------------- |
| **Heading**              | Main title displayed at the top of the section | "Featured Collections"        |
| **View All Button Text** | Text for the bottom button                     | "Shop all Collections"        |
| **View All Button Link** | URL for the view all button                    | "/collections" or "/shop-all" |

**Each category card requires the following settings:**

| Setting         | Description                       | Example                                    |
| --------------- | --------------------------------- | ------------------------------------------ |
| **Image**       | Image filename from Image Manager | category-living-room.jpg                   |
| **Title**       | Category name or heading          | "Luxury Comfort Collection"                |
| **Description** | Brief category description        | "Materials for ultimate comfort and style" |
| **Link**        | Category page URL                 | "/luxury-comfort"                          |

**Responsive Behavior:** The carousel automatically adjusts based on screen size:

| Device            | Cards Visible | Spacing |
| ----------------- | ------------- | ------- |
| **Mobile**        | 1 card        | 10px    |
| **Tablet**        | 2 cards       | 20px    |
| **Small Desktop** | 2 cards       | 20px    |
| **Desktop**       | 3 cards       | 30px    |

{% hint style="info" %}
When you are happy with your changes, don't forget click **Save** and **Publish** to repackage the edited theme.
{% endhint %}


---

# 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://halosoft.gitbook.io/bc-nimo-documentation/home-decor/featured-categories-1.md?ask=<question>&goal=<endgoal>
```

`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.