Next Build Template: Events

[gracekretschmer-metrostar]

Template or Content Type

Events

Example

Drupal CMS:
VA.gov:

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: Does each page have the proper System in the alert/URL/Breadcrumbs/Name/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
• Global: Update DS classes in template #19667
• Breadcrumb capitalization on final crumb does not match prod #19678

[gracekretschmer-metrostar]

Waiting on Sitewide team to review and test changes.

Slack post: https://dsva.slack.com/archives/C07B86KV4P4/p1729540147601049
PR: department-of-veterans-affairs/next-build#795

[gracekretschmer-metrostar]

Staging Review is scheduled for 11/15.

[gracekretschmer-metrostar]

Event Listing will go into production on 12/4 at 7pm EST.

[jilladams]

LAUNCHED! Woo.

[jilladams]

@gracekretschmer-metrostar future project management / ownership question that can be addressed in Jan when the dust settles: we need to figure out how the collective We should be handling the findings identified during testing that were not launch blocking, whether CMS team will really have capacity to help burn them down, or whether their long-term home is in the product team's backlog, to fix as we are able to prioritize them.