Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to Next Build and Content Build Dashboards #19978

Open
1 task
gracekretschmer-metrostar opened this issue Nov 27, 2024 · 0 comments
Open
1 task
Labels
CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status

Comments

@gracekretschmer-metrostar
Copy link

gracekretschmer-metrostar commented Nov 27, 2024

User Story or Problem Statement

As a CMS PO and Engineering Lead, I need to the Next Build dashboard to provide information that I need when speaking to OCTO and VA leadership.

As a CMS PO and Engineering Lead, I need to demonstrate progress on the Next Build implementation in the time to deploy content.

Description or Additional Context

Feedback from Jeff Keene:

  • Feedback: remove “build” from the next build labels.
  • Feedback: add next build metrics to an existing CMS dashboard.
  • Question: can we get baseline on pages (e.g. VA.gov) between Content Build and Next Build to see if we got any performance gains.
  • Question: do we have average time to build a page between Content Build and Next Build?

Steps for Implementation

Acceptance Criteria

  • An updated Next Build and Content Build dashboard that meets the needs to the CMS PO and Engineering Lead.
@gracekretschmer-metrostar gracekretschmer-metrostar added CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status labels Nov 27, 2024
@gracekretschmer-metrostar gracekretschmer-metrostar changed the title Improvements to Next Build Dashboard Improvements to Next Build and Content Build Dashboards Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status
Projects
None yet
Development

No branches or pull requests

1 participant