---
title: Think about filtering with taxonomies
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

[Taxonomies](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) in Xperience by Kentico provide a powerful tool for your customers to categorize and organize content.

Each taxonomy is a _group of related tags_ (e.g., PC features: external GPU, disc drive, tower size…). Content editors assign these tags to content items with a field allowing the given taxonomy. Then they can, for example, configure a widget to display a list of content items with a specific set of tags.

Let's empower your content editors to do just that - filter content items by taxonomy tags in a widget listing.

In the process, we'll cover how you can easily query items of different content types as long as they share a reusable field schema. Let's dive in!

## Consider the scenario

Earlier in this series, we explored reusable field schemas through the lens of content model evolution. You have adjusted your project to work with [two new Article content types](https://docs.kentico.com/modules/advanced-content/work-with-reusable-field-schemas.md#consider-the-scenario) that share an _Article schema_, alongside with a deprecated one.

Perhaps you recall that when you added the _Article list_ widget to your _Home_ page to check your progress and selected a parent page from the content tree, the widget rendered articles of all content types, both old and new.

Now imagine that your customer’s content editors want more control. They’re asking for the ability to filter articles in the widget by specific tags, so they can display only the articles that match the categories they’re interested in.

🎬 [Video](https://docs.kentico.com/docsassets/modules/think-about-filtering-with-taxonomies/filter-articles-finished.mp4)

## Examine the current state

Take a look at the _Article schema_ in Xperience administration. Notice the _ArticleSchemaCategory_ field with the **Taxonomy** data type.
This field allows editors to assign one or more tags from the _Article category_ taxonomy to any content item implementing this schema.

![Taxonomy field in the Article schema in Xperience administration](https://docs.kentico.com/docsassets/modules/think-about-filtering-with-taxonomies/taxonomy-field.png "Taxonomy field in the Article schema in Xperience administration")

The _Article category_ taxonomy already exists in our project and includes two tags: **Animals** and **Plants**. You can find it in the **Taxonomies** application under the **Configuration** category.

![Article category taxonomy in the administration interface](https://docs.kentico.com/docsassets/modules/think-about-filtering-with-taxonomies/article-category-taxonomy.png "Article category taxonomy in the administration interface")

When you examine any of the _Article (general)_ or _Article (interview)_ items in the **Content hub**, you'll see they all have tags or an option to add tags in the **Category** field.