Taxonomy Audit & Redesign

Requirements

As RHD becomes more focused on positive outcomes for Red Hat's various business units, useful reporting will be critical to determining the impact of our publishing work. This will require adding new purpose-based taxonomy to Drupal (e.g. campaign, offer, promotion), cleaning up, expanding, and nesting existing content types, and overhauling the product families and product names: these actions will help us properly aggregate the results of our work.

Screen Recording w/ Narration RE: Draft RHD Taxonomy

Draft Taxonomy Sheet: RHDDX Taxonomy Prep (Adobe_Site-Section)

Epic Leads

• PM - joeschram
• UX - sjcox@redhat.com & tnolan@redhat.com
• ENG - ldary

Stakeholders

• RHD Marketing - dmillsap
• RHD BizOps - rmanchan_jira

Definition of Done

• New taxonomy fields added content types
• Remove no-longer needed content fields from all content types
• Remove all no-longer needed content types
• Ensure consistency of plural vs singular naming of content types (we're using plural naming per jporter@redhat.com)
• Best practices applied. fearlsgroove to define.
• A mechanism is created to tag all content with related Product, Product Version, BU, Project & Portfolio.
• New fields added for "content purpose" per new draft Taxonomy
• Child and parent conventions implemented for media type and for content purpose
  • E.g: RHEL product has a RHEL Product version as a child. Articles have sub-types, such as opinion-article and how-to-article.
  • Needed to query Adobe Analytics to get data on sub-types. "How did all the opinion-articles for the Middleware BU do?"