I have components and pages in my publication, but also I want to implement some categories and keywords in publication.
Is there any reference on this topic?
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It only takes a minute to sign up.Sign up to join this community
The question of why Categories and Keywords are used is more interesting...
The Tridion Taxonomy (the collection of Categories and Keywords) is primarily used to classify the content that you have within the CMS. For example, you may want to classify a News article Component with the location or audience that it applies to. In this situation, you would probably have Categories for 'Location' and for 'Audience', and Keywords within these, such as Europe, Asia, Americas (for Location) or Executive, Developer, Student, OAP (for Audience).
This classification is often used for filtering the content once it has been published to the website.
As Keywords can be nested under other Keywords, and these will all sit within one Category, there is a hierarchy to the Taxonomy. This structure lends itself well to representing content that naturally hierarchical. For example, using the 'Location' example, you may have a Keyword for Europe, which then contains sub-Keywords for Belgium, France, Italy, Spain. Each of these Keywords can then have sub-Keywords again.
You can set a Keyword to being 'Abstract' if you need it, in order to represent an item within the hierarchy, but do not want an editor to be able to classify their content with it.
A third use of Categories and Keywords can be to define a set of constants. For example, the options for a Field within a Component could be "Yes", "No", and "Maybe". Rather than constraining these options within the Schema, you can also set this up as a Category (e.g. 'Choices') with the Keywords "Yes", "No", and "Maybe". This is often done if the same set of field values are available across lots of fields (probably within different Schemas)
Two additional things to note:
Jonathan gives the delivery-side functionality answer. Let me add Content Management side. SDL Tridion's Content Manager has features that use Categories and Keyword:
With Categories set up for text fields in schemas, content authors can then:
The point is the selections themselves are managed, which means you can do create, read/review, update, and delete (respecting dependencies) how these are used across the system.
To take advantage of the above features I would recommend against "Boolean" type fields. Taking a feature-based approach will give you:
So rather than:
Include this feature?
( ) No ( ) Yes
[ ] Feature