Next Build's Events and Event Listing Launch

[gracekretschmer-metrostar]

Status

Update each sprint until completed

Date	Status	Launch Date (see above)	Notes
11/14/2024	in-progress	on-track	resolved blocker, now going through collab cycle ahead of launch
Date of update	not-started, in-progress, done	on-track, off-track	enter brief, blockers, dependencies, etc.

Product Outline

Link

High Level User Story

As an editor, I need to see my content from Drupal CMS get published more quickly and reliability compared to the current process within content build.

Hypothesis or Bet

By moving events and event listings to Next Build, we will see an improvement to publishing speeds and improved stability (less failures) from content build.

OKR

Which Objective / Key Result does this epic push forward?

Objective: Our platforms are the best way to deliver products at VA
Key Result: Our platforms hit the “elite” level (as defined by DORA) on Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service

Definition of done

• Events and event listing are being published from Drupal CMS into VA.gov through Next Build and not Content Build.