Enable a non-blocking process that comprehensively checks CMS content (published and non-published) to identity issues with broken links, accessibility, 508 compliance
Hypothesis/(es)
Broken builds are caused by broken links being included
Linking to unpublished content will cause broken links
Goals
Give Content Editors access to content validation checks prior to publishing
Ensure that one content editor cannot break the build for all CMS users
Measuring Success
[ ] Content Editors can see when their content include links to unpublished content before publishing and deploying
[ ] Content that is published with broken links will not break the build
[ ] CE are immediately made aware if a content validation error occurs after the deployment directly in the CMS.
Charter Objectives Impacted
Content Validation Workflow
Page Previews are available to content editors to use and they include warnings for broken links, accessibility, 508 compliance
A. Previews would work the same as it does currently.
Improved Form and Field Validation help content editors avoid making simple mistakes
A. Includes contextual help based on if the error is something fixable by CE or if it is something that lives in a template.
Post-deployment a series of comprehensive checks are performed and validation errors found are logged and notifications are sent
A. Broken Link Errors, Accessibility, 508 errors
i. Validation Errors are published in the CMS with a linked authors if possible so that proper follow-up can occur
VSP Q1 + Q2 2020 OKR
O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov.
KR3: Reduction in volume of "non-human-needed" support requests month over month
KPIs
Percent of scheduled CMS build deploys that succeed without manual intervention
High Level User Story
Enable a non-blocking process that comprehensively checks CMS content (published and non-published) to identity issues with broken links, accessibility, 508 compliance
Hypothesis/(es)
Goals
Measuring Success
Charter Objectives Impacted
Content Validation Workflow
A. Previews would work the same as it does currently.
A. Broken Link Errors, Accessibility, 508 errors
i. Validation Errors are published in the CMS with a linked authors if possible so that proper follow-up can occur
VSP Q1 + Q2 2020 OKR
O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov. KR3: Reduction in volume of "non-human-needed" support requests month over month
KPIs