search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
99 stars 69 forks source link

[NextBuild] Migrate the [insert chosen feature] to NextBuild #19313

Closed FranECross closed 6 days ago

FranECross commented 1 month ago

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

FranECross commented 1 month ago

Start with someone who knows NextBuild to determine scope of this ticket. Consider how to split up a set of templates so each person can get in there and learn. @FranECross Sync with JR et al to refine this ticket and then circle back around with team to divvy up tickets/features. Need to get an end to end template migrated and to production, or branched and not released so learning is the prioritized.

FranECross commented 6 days ago

Closed as a no op; we'll be making decisions based on best benefits to Content Build.