> For the complete documentation index, see [llms.txt](https://docs.danielvoelk.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.danielvoelk.de/gettings-started/filter-columns.md).

# Filter Columns

I created a video where I explain the process:

{% embed url="<https://youtu.be/Uh6CzOz5ksE>" %}

## Buttons

**Step 1:**

Click on the grey gear icon to access the Button Settings (on the button, that you want to filter with). You can also use images, or any other element to trigger the filtering. It doesn’t have to be a button module.

![](https://tawk.link/603b46ec1c1c2a130d6338d9/kb/attachments/gfAFvPDAu9.png)

**Step 2:**

Go to Advanced → CSS ID & Classes → CSS Class. Here you add the **df-button** class.

**Step 3:**

Additionally add any category that you want to filter with that button like that: **`dfc-[your category]`** e.g. `dfc-cats`.

{% hint style="info" %}
Buttons have to be in a separate section, than your filterable elements. Or you add the **df-buttons** class to your button row (Premium features).
{% endhint %}

## Section

**Step 1:**

Click on blue gear icon to access the Section Settings.

![](https://tawk.link/603b46ec1c1c2a130d6338d9/kb/attachments/bySj6sR2Ub.png)

**Step 2:**

Go to Advanced → CSS ID & Classes → CSS Class. Here you add the **df-area** class.

## Column

**Step 1:**

Click on green gear icon to access the Row Settings.

![](https://tawk.link/603b46ec1c1c2a130d6338d9/kb/attachments/GUEO-_ZyYx.png)

**Step 2:**

In the Row Settings click on the gear icon the access the Column Settings.

I have a four column row, so I see four columns in the Row Settings.

![](https://tawk.link/603b46ec1c1c2a130d6338d9/kb/attachments/xGLQqmscxX.png)

**Step 3:**

Go to Advanced → CSS ID & Classes → CSS Class.

Here you add all the **dfc-\[your category]** class you want e.g. your **dfc-cats** class.

**Step 4:**

Do that for all Columns you want to make filterable.


---

# 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.danielvoelk.de/gettings-started/filter-columns.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.