In this article, we cover how to define content taxonomy.
Topics covered here:
- The need of a content taxonomy
- Tags
- Keeping control of the content
- Automating how the content fills the presentation
Content taxonomy
As your editorial team creates content, you, as a producer, need a taxonomy to:
- Keep control of the content.
- Automate how content fills the presentation.
Tagging content meets both the needs above.
Note: Tags tie together content and presentation, allowing you to dynamically assign content to pages.
Tags
Tags are metadata you can assign to every editorial entity to describe its content.
You can
- Create tags in the FORGE Back Office.
- Import tags from an external source through API.
Tips:
- In brackets, the tag label displays the tag slug. E.g., in the tag label alpha (alpha), the alpha in brackets is the slug.
- Selected tags link to the tag detail page. E.g., select the tag alpha (alpha) to open this tag's detail page.
- The warning icon
displays next to selected tags that are not published. See tag alpha in the world (alpha-in-the-world) in the screenshot below:
- When tags belong to folders, editors can explore the folders structure and set as favorites the most used folders. Once set in a page — e.g., in the editorial selection detail page - favorites folders are available everywhere across FORGE Back Office.
Keeping control of the content
As a producer, the content taxonomy labels the new-coming content and facilitates its management. You can:
- Search content by tags
- Perform bulk operations by filtering by tag
Reference scenario
Consider the following primary taxonomy of content for the website and app:
- Tag website-news the latest news articles for the website
- Tag website-news-old the news articles to archive for the website
- Tag app-news the latest news articles for the app
- Tag app-news-old the news articles to archive for the app
Assign the content-website authorization group to tags website-news and website-news-old. Then, only users with the content-website authorization group can see entities that have one of those two tags.
Do the same for tags and authorization groups that relate to the app.
Automating how the content fills the presentation
The presentation relies on the content taxonomy. This dynamically links content to the page it's set to display on in the front-end.
There are two ways to define how content in a module displays:
- By selecting an entity type and the unique identifier (the slug) of the content of that type. In this way, regardless of the content taxonomy, you predetermine what content the module renders. Use it to assign static content to a page.
- By selecting an entity type and a set of tags. In this way, you determine that the module renders the content of that type with those tags. Use it to assign dynamic content to a page, which displays entities based on the content taxonomy.
Reference scenario
The taxonomy above allows you to automate news articles assignments to the presentation pages. Tags website-news and website-news-old relate content to pages under the folder website. Instead, tags app-news and app-news-old relate content to pages under the folder app.
E.g., the index page under website relates its module Editorial List to the stories with the tag website-news.