User story:

As a developer, I want to define a content type as taggable via configuration. Once I have defined the content type as taggable I expect most (ideally all) tagging functionality to be available automatically without further configuration: the light dialog and the tagging field should launch when I press the keyboard shortcut in my app; the tags column should be added to my workbench automatically; and the Edit tags action should be added to the action bar.

Tasks:

• Create a JCR mixin mgnl:taggable
  • declares a multi-value property named mgnl:tags []
  • tentatively of type WEAKREFERENCE (uuid without referential integrity)
• Allow a developer to define what content is taggable using the new taggable mixin.
• Do a spike to see how far we can go if we just condition the feature against the presence of the taggable mixin in the node type definition.
• Define tours in the travel demo as taggable content so we can test and demonstrate the functionality.

See: Tagging content: Technical prerequisites, recommendations