[MVP] New pages for improved product experience

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.

tnolan & 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

RHD Product Page Experience - Assemblies Inventory

Epic Leads

• UX - sjcox & tnolan
• PM - jschram-1
• ENG - aarreola@redhat.com
• RHD Marketing - mguerett & dmillsap

Stakeholders

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

Acceptance Criteria

• The "New World" product page type is available in Drupal, authors can create pages that contain a short, developer-focused product description, a prominent link to the corresponding page on RHDC, curated gallery of Quickstart technical articles, a big red "Download Now" or "Try It Now" button up top, and breadcrumbs to related products or product bundles/portfolios. Authors can also create and insert comparison charts between the product and one or more upstream projects (including CTA links to the upstream project(s), and a statement about the value proposition of the supported product.)
• 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 "solo" Product Page… OR (possible alternative) author choose new "Product", then in the new product page, author chooses product type: solo (component) or portfolio.
• 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 name.
• Author creates short developer-focused description of what the product allows, added as Markdown or unformatted text
• Author uses assembly to add on-page images
• Author pastes link to the equivalent page on RHDC.
• Author customizes page slug to align with product name and search goals.
• Author uses assembly to add hero image or the product 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 "Supported Product Value Prop"
• Author uses assembly to add product comparison chart with CTA links
• Author uses assembly to add Contact Sales CTA
• Author uses assembly to add upstream project name and logo for use in the comparison chart
• Author adds big red download button or big red "Try It Now" SaaS button—big buttons have offerID fields in Drupal.
• Author publishes Product Page
• All Products page is updated with new Product
• Product Taxonomy in Drupal is updated with new product tag for Purpose Attributes see DEVELOPER-5227