Last Updated 3/6/2018
Tags provide an intuitive mechanism for grouping related content together.
Tags are primarily intended for relating content together for display in a common area on the frontend of a website. The same can sometimes be accomplished using folders, except that content can only have a single folder while it can have multiple tags.
Not all tags have to be displayed on the frontend of the website. Depending on the complexity and needs of the website, you may have tags that you use for their functionality rather than for display. There are two common and simple strategies for determining which tags to display - the first is simply to display all tags: "If the editor tags it, display it." This most obviously applies to blog posts, but may also apply to articles, calendar entries, images, documents, snippets, authors, and more. The second strategy for determining which tags to display would be to only display tags that have urls.
Naturally, it is easier to say, "display it," than it is so decide how to display it. While that should largely be up to your designer and content strategy team, it may be up to you as the developer to bring up the possibility of tagging multiple object types and discussing what that means on your site early in the process.
Additionally, as mentioned in a previous lesson, consider making a page for each tag. While it may seem easier at first to simply utilize an existing template (eg: your blog template) by modifying it slightly to accept query parameters, that strategy is likely to prove inflexible over time and has a number of drawbacks over using a tag-specific template on a tag page.
Let's work together to make our documentation as helpful as possible.