Open FranECross opened 2 months ago
@FranECross Find any past research, content models or mural boards.
Some relevant Facilities events epics you may want to cross reference/list under here
Update 6.7.24
Related: Initiative - Vet Center design 2.0
Problem to be solved
We launched the current version of Events with the site re-launch in 2018 using mostly out-of-the-box Drupal functionality. While this worked for the initial MVP, as the site has grown problems due to the nature of the site (decoupled) along with growth of how we use events calendars has limited the life-span of this content.
For events v3 we will:
Defiinition of done
We expect that this initial (MVP) work will have minimal-to-no visible Veteran-facing impact on the Front-End. The react application should use the existing design and only be updated to solve for accessibility problems and any design components that have been updated since v1 was launched.
Monthly updates:
Headlines
VA stakeholders -
OCTO lead - Public Websites Team/Dave Conlon
Is this initiative tracked to an upcoming event or congressional deadline? - We are tracking toward end-of-Fiscal Year to enable Vet Centers in particular to publish relevant events.
Details
Which OCTO team should do this? When might they have time to do this? - Public Websites - Late Spring/early sumer 2024.
Which OCTO or portfolio priority does this work support? - Improve satisfaction of our Platform Users (high demand from editors)
What is the user impact and scale of impact? - Veteran-facing: We anticipate the ability to raise awareness of Events by about 20-25% at-launch when capability is added to Vet Centers.
What's the long-term plan for managing this effort? - this product will be owned by Unauthenticated Experience.
What funding/contract support would this need? - Existing sitewide contract.
What else do we need to know in order to decide if/when we can do this work?
Reference links:
Events v3 entails:
Back-end
Front-end
Out of Scope for MVP
Problems to Solve:
Misc Notes:
Questions:
Information & Research
Questions:
User Story or Problem Statement
As an editor who creates and publishes events, I need to be able to publish the events faster and more efficiently so I can get the event information in front of Veterans, their caregivers, families and survivors in a more timely fashion so that they can make appropriate plans to decide which to attend and actually attend.
Affected users and stakeholders
Hypothesis
We believe that an Events API and endpoints will will achieve faster publishing of events to VA.gov, enabling Veterans to attend more events as they will have more time to plan attendance.. We'll know that to be true when we see an increase in people signing up to attend events, and/or by looking at Google Events for VA.gov Event click activity.
Outcomes:
Front-end:
Acceptance Criteria
Change management triage
The change represented by this user story will:
If you selected an item above, use the Change Management Runbook to create a CM epic and associated tickets.
If you did not select an item above, update issues/PRs in GitHub but don’t plan for change management.
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