Next Build Template: News Release

[gracekretschmer-metrostar]

Template or Content Type

News Release

Example

https://dev.va.gov/southern-nevada-health-care/news-releases/va-southern-nevada-healthcare-system-to-host-annual-veterans-appreciation-day-car-show-bbq/

Description

Overview of template or content type, including relevant details to the migration lift.

Owning Team

• CMS team
• Sitewide
• IIR

Definition of Done

Data:

• Conditional logic matches content-build / production
• SEO Metadata matches production
• Analytics match production

Interaction / Behavior:

• Interactions / behavior match production (e.g. accordion expansion by default on page load if they do, data IDs on elements / their usage, link behavior, form / input field behaviors, etc)
• Lovell Logic: Do the Tricare (/lovell-federal-health-care-tricare/) and VA (/lovell-federal-health-care-va/) variants of each page have the proper System in the
  • alert
  • URL
  • breadcrumbs
  • left nav
• VA Manila (/manila-va-clinic): do the pages appear properly and respect the custom IA, including:
  • URL
  • breadcrumbs
  • left nav

Accessibility:

• Accessibility experience matches production (voiceover/screen reader behavior, appearance at 400% zoom, params on elements, etc)
• axe devTools output matches production

Visual presentation:

• Design system components, prop usage and component versions match production
• Design (font size, spacing, Anything else?) matches production
• Review all breakpoints

Signoff / Launch

• Owning team has reviewed the build and provided feedback / approval
• CMS Team has confirmed launch readiness

ADDITIONAL CHILDREN

The tickets below also were found during QA of this product template, but apply to multiple products, so are listed in the cross-product epic, #20178.

• Next-build Manila: Facility sidebar menus should show #19762
• Next-build Manila: page <title> is incorrect #20148
• MUST: Next-build: Mobile footer accordions do not open when clicked #20159
• CONSIDER: Cross-product Next templates: Issues with mobile header search styling #20158
• Global - Markup for banners has incorrect ARIA #20161
• Missing Analytics on Feedback button #19771
• Global: <next-route-announcer> element - possibly accessibility issue #19679

[jilladams]

Verifying Manila will be blocked on #19570

[jilladams]

To my knowledge we haven't been provided a build of News Releases to review. (I know News Release Listings was noted as ready for review, but there too, we weren't sure where to find it to review, noted here.)

[laflannery]

Noting for future selves:

• Currently on the content-build templates, there is an empty <nav> element that causes accessibility issues (See ticket for more details). This has been removed from next-build so I'm going to close that Sitewide ticket
• Manila does not currently have any News release details so this wasn't able to be tested. It's just something we will have to pay attention to when they do add some, if this happens between the QA time and the launch time

[laflannery]

@jilladams This should be all done but there are some global issues that I don't know if I need to re-ticket? Should I just list them all in a comment or something?

[jilladams]

No dupe tickets, pls. If you find that a global issue is present on the Next build of a product, can you make sure that the product and next-build are added to the global ticket as labels? ANd yea, maybe just link those tickets on the relevant epic for the Next version of the product.

[jilladams]

And if that doesn't make any sense, let's chat for a min to figure it out.

[jilladams]

@EWashb @mmiddaugh @gracekretschmer-metrostar : Sitewide has completed testing News Releases, and filed all our issues with suggestions about Must / Should / Consider. THey're linked in the Epic as sub-issues if they applied only to News Releases, and in the "Additional Children" section of the ticket body if they happen on more content types than just News Releases.

I'm not sure we have a Go / No Go process yet. Let me / @laflannery know if you'd like a live review of the opened tickets, to decide if y'all agree on the Musts that would block launch. If we also want to talk ownership of blocking issues, we should include @Agile6MSkinner.