jilladams
commented
1 year ago @laflannery @wesrowe was reminded today that this epic already exists for us to begin aggregating notes on future improvements needed / assessment of issues with the Header. Added the ARIA issue.
Background
User Story or Problem Statement
The headers on VA.gov have undergone significant development, including the implementation of a mobile-only header. We seek to understand these implementations so that we can improve them and potentially remove tech debt.
Acceptance Criteria
Design principles
Veteran-centered
Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.Accessible, plain language: Provide guardrails and guidelines to ensure content quality.Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.Editor-centered
Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.Efficient: Remove distractions and create clear, straightforward paths to get the job done.Approachable: Offer friendly guidance over authoritative instruction.Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.Empowering: Provide clear information to help editors make decisions about their work.Runbook