search

cityofaustin / techstack

Project management for the City of Austin's new digital service delivery platform, Austin.gov.
11 stars 3 forks source link

Tag creation that results in filtering ability for official documents and elsewhere #4646

Open toribr opened 4 years ago

toribr commented 4 years ago

Publishers and admins need a way to create a custom taxonomy that can then be used for filtering documents. Secondarily, these tags could be used to push content to the contextual personas we have mapped out.

Devise a method in Joplin which allows the creation of a taxonomy which can then be applied to pages. Probably a list of no more than 12 items. The list will need a title, since pages may actually need multiple tags.

Tag widgets for MVP will be department specific initially, but post MVP may need to be shareable (this would enable tagging across the site and help prevent dept silo-ing.)

This issue is two fold: • UI by which a tag taxonomy is created • UI which then appears on pages. In some cases, only one selection should be made, ie, page type (formal complaint). (MVP) In other cases, multiple selections might be appropriate, ie, persona/contextual contexts. (Post MVP?)

Questions: • What pages in a dept get tags? Are they controlled at an admin level? If they are available via streamfield, then how will authors know to add the necessary tagging?

toribr commented 4 years ago

Punting this issue for now. Moving to backlog. For the purpose of official documents, content will create topics which hold official document collections that contain each document type.