New world Product Group page template

Requirements

Our current Product Pages are not serving the needs of our audience, or our Business Unit partners. The audience needs these pages to be more focused on Quickstart material, the BUs need us to tell more complex stories that include product portfolios, solution selling, and the connection with the upstream needs to be more explicit. One more important detail: we're coordinating this work with red-hat-doc-com (RHDC) who is overhauling their product pages at the same time—the idea is that we'll be cross-linking pages in order to take the weight off of each site to have to be all things to all people.

In addition to Product Pages (which we're creating on DEVELOPER-5201, we need to make a variant called the Product Group page—this is a superset of Product pages that are aligned to how the product portfolio is being marketed. That's the purpose of this Epic.

tnolan@redhat.com & gdoyle-1 have started the primary research on this work…see their results in these two documents below.

Product Experience Competitor Review

DevConf: RHD Product Experience Data & Analysis

Epic Leads

• UX - tnolan@redhat.com
• PM - joeschram
• ENG - aarreola@redhat.com
• RHD Marketing - mguerett & jessk_jira & @David Millsaps

Stakeholders

• Paul Hinz (MW)
• James Faulkner (MW)
• Trisha Ristagano (MW)
• Colby Hoke (RHDC)
• Laura Hamlyn (RHDC)
• Ellie Johnson (RHDC)

Acceptance Criteria

• The new Product Group page type is available in Drupal, authors can create product group pages that contain a short, developer-focused product description, a prominent link to the corresponding page on RHDC, curated gallery of Quickstart technical articles, launch a SaaS Try-It-Now Experience, and breadcrumbs to component products. Authors can also create CTAs for contacting RH Sales about product group pricing.

Review Steps

• Author creates a new Product Group page… OR (possible alternative) author choose new "Product", then in the new product page, author chooses product type: portfolio or solo (component).
• Author creates page headline that aligns with product group name.
• Author creates shot developer-focused description of what problem(s) the the product group solves, added as Markdown or unformatted text
• Author uses assembly to add on-page images
• Author pastes link to the equivalent product group page on RHDC.
• Author customizes page slug to align with product group name and search goals.
• Author uses assembly to add hero image or the product group logo (or video if apropos) or selects an existing product image from the Drupal media library (image or video required)
• Author uses assembly to add on-page images or videos
• Author uses assembly to add "Componenet Products"
• Author uses assembly to add Contact Sales CTA
• Author adds big red "Try It Now" SaaS button—big buttons have offerID fields in Drupal.
• Author publishes Product group Page
• All Products page is updated with new Product Group
• Product Taxonomy in Drupal is updated with new product group tag for Purpose Attributes see DEVELOPER-5227