Closed davidmpickett closed 5 months ago
Goal for MVP is to be able to handle multiple paradigms for system phone numbers (one, many). Reviewed mural.
We previously suggested shortname treatment in #15490 (vba_short_names.xlsx) Notes updated in #15752
CMS Collab Cycle says we must show error messages. Jordan has proposed updates. Michelle / Erika haven't had time to discuss. Michelle to follow up & we can revisit next UX sync, when design ticket is in review state.
Alexis / Jordan to follow up offline re: refining tickets / getting organized. Alexis to try and attend as many training sessions as possible. Alexis / Jane to sync on tickets.
Next projects for Jordan:
Police Midpoint feedback Captured in tickets.
If time allows
Notes:
Notes:
Notes:
Notes:
Notes:
Notes:
Notes:
Notes:
Goals
Links
Notes Map design tickets
Error states ticket
Goals
Links
Notes
Goals
Links
Notes
Goals
Links
Notes
Goals
Links
Notes
First 30 min before @aklausmeier and @mmiddaugh leave
Second half
Notes:
Notes:
Notes:
Notes:
Proposing breaking up #s into 2 sections:
Billing & Insurance treatment: For Pay in Person section on Billing pages, e.g. https://www.va.gov/gulf-coast-health-care/billing-and-insurance/, want to break up the presentation when multiple locations have hours / contact info under Pay in Person. (e.g. main location + Cashier's cage.) Jordan's design proposes using card component again. Alt treatment proposes using an accordion per location.
Amanda to review. Concerned re: card treatments, and wants to make sure accordions are consistent with VBA.
Also proposing putting this into an accordion. States:
Next step:
99% sure the CMS Collab Cycle will change again, now that they're on Platform. Check with Grace / Michelle before moving on any CMS Collab Cycle action steps.
Dave to schedule meeting with engineers and product
Error states:
Sitemap / tree based on Minneapolis has been developed in Google sheet. (Will move to SharePoint eventually.)
@mmiddaugh to share analytics for entry point analytics to understand how people tend to arrive on VAMC sites (direct from google vs from Va.gov)
Q: Do more stable places make more sense than areas of the site that vary a lot? A: More stable areas might make most sense, to get a sense of valid results for testing
Q: Add to "Manage your health online" section? (System page) A: Seems like a viable option
Q: Is it smart to deliberately put it in some bad places, to prove out in the data that those are bad places? A: Yes maybe. Alexis will consider.
Amanda hopes by tomorrow to provide feedback on placements. Link for ref: https://mobile.va.gov/app/va-health-chat
Bottom line: do we need the 3rd line? Seems no.
307 facilities in the Facilities API have some data in the 3rd address line.
Will be very difficult to predict how these get used, or quality control that.
Hide for now, bc this is a config level change. Let's allow each product to expose it / use it correctly.
Amanda to brief Michelle on her discussion with Dave. Questions are around whether folks wh have more than 1 service location will have to go in and set their options within each service location. Q: are there other things we would like them to handle at the same time?
Do VAMC editors need a training on this in office hours? Maybe.
Notes: In the spotlight card Component: to replace blue spotlight boxes
Major Links
component, but not every spotlight includes links. Some spotlight cards use bullets, etc. The content irl is more complex than that component.card
component. Card component also requires a link. In the Spotlight links list:
Related links
component For reference: on Health Services List, spotlight cards exist but are more scructured in Drupal. Named "Featured content on health-services page" (using Drupal paragraph "link teaser"): contains a link, link text, link summary.) There is a ticket for reviewing the Drupal interface to get aligned.
Next step:
Notes:
Notes:
“Name of office or location" field left blank:
Labels show without other information: Update Drupal UI to be more clear about required info.
Hours
1 vs 2 service locations at one facility
1 vs 2 facilities listed on a page
Visual hierarchy change - change headers to bold text.
Labels being duplicated: Hard. Not yet solved.
Next steps:
Notes
#17350 is the epic tracking Service Location UX work now.
@davidmpickett @aklausmeier As I'm updating calendars, I'm penciling in process we've bandied about. This is not in stone and can be revised, but: I've spun up a ticket to convert this to become Sitewide UX Sync as of next week, and am framing the calendar invite that way. We can change this after kickoff discussions take place: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17669
@jilladams @davidmpickett Does this thought process also include scrapping Public Websites UX refinement and rolling into the Sitewide UX sync?
Follow up notes will be in https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17669
Jump link to latest agenda
https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16586#issuecomment-2023110872
Meeting Purpose and Structure
This is a weekly meeting where we focus on the following actions:
Meeting logistics
Agenda
Attendees