Although Platform is moving away from content build and toward next build, we may need to publish the most current deployment info on both systems so engineers are able to successfully use whichever is appropriate.
Tasks
[ ] Audit website docs for Content Build deployment info
[ ] Contact CMS team for deployment schedule
Acceptance Criteria
[ ] What will be created or happen as a result of this story?
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Pain Point
VFS Front End engineer commented in Q2 Survey: "Documentation for content-build deployments (https://depo-platform-documentation.scrollhelp.site/developer-docs/deployments) is incorrect and has not kept pace with the recent deploy time changes."
Relevant links:
Platform All Feedback Repository
Issue Description
Although Platform is moving away from content build and toward next build, we may need to publish the most current deployment info on both systems so engineers are able to successfully use whichever is appropriate.
Tasks
Acceptance Criteria
[ ] What will be created or happen as a result of this story?
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)