Vocabularies are a Navigation Item, part of the site’s taxonomy, that provide a way to classify a website’s content. Vocabularies may be promoted in the site’s main navigation and/or off-canvas navigation bar but this is not very common.
Vocabularies are used to group, organize, and categorize a set of rich terms. So they can be thought of as a parent or root container for terms. For example, you may have a vocabulary titled Recipe Cuisine which includes terms such as American, Ethiopian, German etc.
Vocabularies are typically established as part of the site migration but can also be added to a site post-launch. Post migration, the creation/modification of vocabularies is handled by the support team. There is no interface to manage vocabularies from within the CMS at this time.
Vocabulary hubs can be promoted as a primary Navigation Item but this is not very common. Such use cases are Women A-Z on Maxim or Groups on Bio. In both of these cases the vocabulary hub is used, displaying a list of terms that are included in that vocabulary.
We currently do not have a UI within the CMS to create and manage vocabularies. Any requests to make changes to vocabularies and/or create new vocabularies post-migration should be sent to Publisher Support.
That said, if a site wants to see which vocabularies they have created they can visit the Vocabularies & Rich Term manage content screen. By selecting from the dropdown options, they will see all of the vocabularies that have been created for their site. They can then drill down into that vocabulary to see the rich terms contained by any particular vocabulary.
For any site, we recommend the following default vocabulary but it is not required:
Rich Terms - This tends to be a catch all vocabulary for any generic tagging of terms a site would like to apply to their content. This vocabulary is typically associated with Content Articles but can be associated with all content types. If this is only associated with articles, that means that only articles will appear on the rich term hub pages. If this vocabulary is associated with all content types, that means that the rich term hub pages can include a mixture of content types.
For a site using Recipes, we require the following vocabularies since they map to structured data used for SEO:
Recipe Category - The category of the meal this is relevant for. For example, breakfast, brunch, dinner etc. This maps to the schema.org property recipeCategory.
Cooking Method - The method of cooking used in this recipe. For example, Frying or Steaming. This maps to the schema.org/Recipe cookingMethod.
Recipe Cuisine - The cuisine of the recipe. For example, French or Ethiopian.
We do not have any other default vocabularies and/or required vocabularies for any other content types currently on Tempest.
Adding Vocabularies to Content Types
Vocabularies can be associated with one or more content types. Some sites may want to have a “Rich Term” vocabulary shared across all of their content types ie. articles, recipes, and videos. Other sites may want to only have one content type affiliated with the “Rich Term” vocabulary ie. only articles. This decision is driven by whether or not the site would like to show a mixture of content types under a specific term.
Rich Terms can be used for ad targeting purposes. For example, you could run a campaign against all content tagged with the rich term "advertiser". In order to use that single rich term across all content types, it is a best practice not to limit the content types by vocabulary.
Once a vocabulary is assigned to a content type, content creators will be able to choose to assign a term from that list to their content. Content creators can also dynamically create new terms within that vocabulary and assign it to that content type from within the editor.
A site can have an unlimited number of vocabularies. Each vocabulary can contain an unlimited number of terms.
We can prevent terms from being created dynamically from within the editor UI. This is especially helpful for vocabularies that have a closed set of data. For example, months in a year or astrological signs.
Rich Terms Summary
Rich Terms are a Navigation Item that are used to organize and classify content. They are contained by vocabularies which define the collection of terms at a higher level. For example, the vocabulary may be Meal Type while a term in that vocabulary may be dinner. Rich Terms can be promoted in the site's main navigation bar or off-canvas nav.
Terms offer several benefits to a site including:
- Flexibility: Rather than only having the ability to classify content based on it's location in a hierarchical structure, terms allow unstructured classification. This allows users to select as many terms as necessary to accurately classify a piece of content, allowing it to live in more than one location. This also allows users to create new classifications dynamically.
- Discovery: Terms can be thought of as representing the index of a site, allowing readers to quickly locate topics of interest via the site's search and/or the terms listed at the end of content. For example, if a user wanted to see all the chicken recipes on a site, they may search “Chicken Recipe.” In that example, “chicken” would be the term and "recipe" would be the location in the hierarchical structure. Having terms listed at the end of content is also really helpful for users to navigate to the term hub to see other content in that same collection.
- SEO: Properly tagged content can have great benefits for SEO. Similar to powering a site's search, accurately tagging a piece of content with relevant terms will help surface this content on search engines.
Like vocabularies, Rich Terms are migrated to Tempest as part of the site onboarding process. They are also actively created as part of the authoring workflow on Tempest.
Rich Terms vs. Tags
It is important to understand the terminology we use on Tempest versus the industry terminology when it comes to rich terms and tags. On Tempest, we have a clear distinction between what these two concepts mean and how they exist on the platform.
We used to have a concept of tags on Tempest. These tags were super basic and would carry no meta data associations. For example, you would see a tag at the end of a piece of content but this tag would not link to a tag hub, you could not apply a special layout to a hub, there was no richness to the tag concept where you could have a hub with additional content and imagery creating a richer collection. They were simply labels at the end of content that denoted something about the content on which it was associated but essentially did nothing.
The idea of rich terms came from the desire to have metadata around the tag itself which we previously did not support. So we deprecated the notion of tags to move to a concept of rich terms. The terminology was changed from "tag" to "rich term" mostly to distinguish the two items internally as independent concepts. Rich terms are applied to content in the same way as tags and they also appear at the end of content as a list. But rich terms are in fact "richer" since they can carry metadata. Rich terms lead to hub pages that can have overview text that serves as copy to frame the collection of items in the hub. Rich term hubs can also have imagery, have special layouts etc. All of this functionality did not exist for tags.
On the rest of the web people refer to what we call "rich terms" as tags or terms. The terminology distinction is mostly for internal purposes since these two existed as separate concepts and have/had separate functionality.
Deleting Rich Terms
Let's say you've misspelled a rich term, or just don't want it in your bank of rich terms anymore, deleting the term is a simple process.
1. Click on Vocabularies and Rich Terms
2. Next click on the rich term that you want to delete.
3. Select "Delete" from the dropdown.
The rich term will no longer auto populate, so you cannot make the mistake of accidentally clicking on the misspelled or unneeded term.