-
Notifications
You must be signed in to change notification settings - Fork 70
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
[EPIC] Add Events to Vet Centers #12926
Comments
From 9/13/23 Vet Center Office Hours:
|
10/17 Q4 discussion: Events ownership:
PrioritiesVet Centers: has no access to PDFs / other means to advertise events til this ships, so urgency is high, and frequently requested in office hours. Timeline should keep that in mind. Requirements gathering / scopeResearch: do we need both Editor and Veteran data to support next steps for Events UX? VBA / Vet Center Editors:
Alexis & Amanda have done generative research work like this, to understand needs of people doing the work to understand the service design aspect. Can be beneficial to interview similar role / scope / environment people to create a safe space for folks to be honest.
VAMC: Technical / templatesDrupal: expose Regional Offices & Vet Centers as optional VA facilities for Event locations Filters: Known issues#9438 - SuperEpic for Public Websites that aggregates all the visions for Events that are not prioritized. Includes an epic of UX feedback from VAMC editors. Next step
|
@davidconlon @aklausmeier two event use cases from Drupal CMS office hours today
|
also this: #17529 [CONSIDER] Event reminders and subscriptions |
Closing Events loops as we talk Events in Q2 @davidconlon @mmiddaugh :
So worth noting on Facilities side that before we begin build for VBA / Vet Centers, we should (continue) be(ing) mindful that the whole Events product is in flux and may require revisit of FE builds / design if Events react app shapes up before we get to building. |
From Michelle: we should consider breaking Vet Center / VBA events apart. TODO: @jilladams |
VBA Events epic created: #17665. Added note to ticket body. |
Have added this to #17661 epic for Vet Center 2.0 design, since we expect Events to ride along with that effort, generally, now. |
Background
Front end and CMS redesign and IA
Use cases
As an editor, I need a way to communicate events and/or observances, which may be recurrent or one-off.
This work is dependent on a publishing capacity that is defined by being able to publish within 60 minutes, directly related to node capacity and drupal stability.
Considerations
Veteran experience Goals
Decision log
The text was updated successfully, but these errors were encountered: