Skip navigation

Organizing your content with taxonomies

As your projects grow bigger with more and more content, you might want to do more than just find specific content.

Table of contents

    Taxonomies offer a versatile and customizable way to organize your content. Here are examples of their usage:

    • Content releases – group your content items as they are to be published in upcoming releases.
    • Subprojects – group your content items into subprojects (every content item can be assigned to one or multiple subprojects).
    • Business-specific categories – create categories such as Article tagsIndustryCar brandsPersonas, etc.
    • Website hierarchy – use taxonomy to represent your website hierarchy and assign content items to their locations in the hierarchy.

    Getting organized with taxonomies for release publishing

    In this tutorial, you will learn how to use taxonomy for content releases. Working with taxonomies is similar to using tags. By tagging content items with a taxonomy term, you can organize the items into a group and work with them as with a single release. Taxonomy terms are organized in taxonomy groups, which can represent a group of releases, whereas each taxonomy term would be one release.

    For example, let's say you have an upcoming pricing update that you'd like to reflect in a few content items. First, you need to create a new taxonomy group with a taxonomy term for the particular release. Then add the term to the content items you'd like to release for the pricing update. This way, you get the items assembled together into one release group.

    Creating a taxonomy group for releases

    To create a taxonomy group named Releases with taxonomy terms:

    1. From the app menu, choose .
    2. Click the Taxonomy tab.
    3. Click Create new on the right to create a taxonomy group.
    4. Type Releases into Taxonomy group name.
    5. Click Create new Taxonomy term.
    6. Type a name for the taxonomy term.
      • You can create a hierarchy of dates with releases nested under them.
        For example, Q3 > Pricing update.
    7. Click Confirm to add your taxonomy term.
    8. Repeat the last three steps to create enough taxonomy terms, one for each of all the planned releases.
    9. (Optional) To organize the terms in a nested list, drag them using the button. Parent terms can represent years and their quarters.
    10. Click Save changes to save your new taxonomy group.

    You have created the Releases taxonomy group with the taxonomy terms representing individual releases. But the terms still need to be connected with content items.

    Applying taxonomy to content

    The following steps may differ depending on whether you have already created your content types and content items or not. If you're just starting with the project, learn how to create a new content type and a content item first.

    Applying taxonomy to content means tagging content items with taxonomy terms. But to be able to do so, you need to add a Taxonomy element to a content type(s) on which the content items are based. Follow these steps:

    1. From the app menu, choose .
    2. Open a relevant content type for editing.
    3. Insert a Taxonomy element.
    4. In the element choose the Releases taxonomy group.
      To add more taxonomy groups to one content type, insert more Taxonomy elements.
    5. Click Save changes.
    6. From the app menu, choose .
    7. Open a content item based on the content type for editing.
    8. Find the element Releases and select the term representing a particular release. This will "tag" the content item with the taxonomy term.

    You have applied the taxonomy group to the content type and tagged the content items with the taxonomy terms. So now you are able to use the Taxonomy filter in the content section.

    Filtering content for release

    To filter out content using a taxonomy group:

    1. Go to .
    2. In the Taxonomy filter settings, choose a taxonomy term representing a desired release.

    Later, when you are about to publish your work, filter out content items of required release and publish them all at once instead of searching and publishing them one by one.

    You can use taxonomies similarly for grouping them into subprojects or in any other way that suits your needs.

    What's next?