[NextBuild] Migrate [insert chosen feature] to NextBuild #19385
Labels
Accelerated Publishing
Needs refining
Issue status
Public Websites
Scrum team in the Sitewide crew
sitewide
VA.gov frontend
CMS team practice area
Description
The first product feature to be implemented using NextBuild is the Resources & Support content type of Checklist.
The AP team doesn't have capacity at this time to provide focused time or information, so this ticket is for one PW engineer to choose a PW feature to migrate to NextBuild.
The work encompassed in this ticket will entail exploration and laying a lot of groundwork. Given that templates can share common pieces (such as paragraph types), we might end up with duplicate work, but maybe engineers could pick ones that don't have any overlap, if possible.
Note the addition of a QuickStart guide link below in the Artifacts section.
Background
User Story or Problem Statement
As a Sitewide engineer, I want my work to use the latest technology and fastest build system, for maximum efficiency and Veteran value.
As a VA Product Owner, I want my technical products to adopt Accelerated Publishing, to move toward deprecation of content-build as soon as possible.
As an Editor, I want my content changes to be published as quickly as possible, for maximum Veteran access to the latest correct information.
Status / Change management stakeholders
Each Sitewide product will require migration to new templates. Editors who create content in these types will require change management to be aware when the changes are deploying and of the change in behavior for publishing timelines.
Stakeholder / Editor groups are listed below for visibliity, but each group may require its own sub-epic and change management.
Engineering notes / background
Artifacts from Accelerated Publishing Team (in Github)
Analytics considerations
Quality / testing notes
Acceptance criteria
The text was updated successfully, but these errors were encountered: