Skip to content
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

Update designs for facilities with complex names #15660

Closed
5 of 8 tasks
davidmpickett opened this issue Oct 12, 2023 · 11 comments
Closed
5 of 8 tasks

Update designs for facilities with complex names #15660

davidmpickett opened this issue Oct 12, 2023 · 11 comments
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide UX Vet Center CMS managed product owned by Facilities team

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Oct 12, 2023

User Story or Problem Statement

Facilities sometimes have multiple name or multi-part names. Right now, this complexity is only displayed on the facilities' main page, and not in the other places it is listed across VA.gov.

We need to ensure that facility names are consistently displayed across VA.gov

Design

Vet Center example

Official name: Dr. Cameron McKinley Department of Veterans Affairs Veterans Center
Short name: Prescott Vet Center
H1-associated text: Also called the Dr. Cameron McKinley Department of Veterans Affairs Veterans Center

VBA examples

See VBA IA ticket for more context
Official name: Salt Lake City VA Regional Benefit Office at George E. Wahlen Department of Veterans Affairs Medical Center
Short name (h1): - Salt Lake City Regional Benefit Office
Shared location (h1-associated text) - at George E. Wahlen Department of Veterans Affairs Medical Center

Description or Additional Context

Vet Center main page

Screenshot 2023-10-12 093823

Vet Center Locations Page

Screenshot 2023-10-12 093841

Other nearby facilities lists

Screenshot 2023-10-12 095741

Facility locator results page

Screenshot 2023-10-12 093807

VA.gov Search results

Screenshot 2023-10-12 094511

Google search results

Screenshot 2023-10-12 100741

Acceptance Criteria

  • Facilities designs in Sketch are updated to show expected behavior for facilities
  • Review with Amanda K.
  • Review with a11y
  • Review scheduled for next UX sync

Team

Please check the team(s) that will do this work.

  • CMS Team
  • Public Websites
  • Facilities
  • Accelerated Publishing
@davidmpickett davidmpickett added Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status UX Regional office CMS managed VBA product owned by the Facilities team Vet Center CMS managed product owned by Facilities team labels Oct 12, 2023
@davidmpickett
Copy link
Contributor Author

@jilladams @xiongjaneg Candidate for sprint 96 based on UX refinement

@xiongjaneg
Copy link
Contributor

@thejordanwood Would you please review and update the description and ACs as needed? If you have enough info, would you also please estimate points (in case this is ready for next sprint)? If you want to meet to discuss this, please let me know. Thank you!

@thejordanwood
Copy link

@davidmpickett To double check that I'm clear on this:

  1. We want to primarily display the short names on main facility pages, locations pages, Other nearby facilities lists, the Facility locator results page, and search results.
  2. We want to show the official names as h1-associated text on main facility pages, like in the Prescott Vet Center example. Is that the only place we need to show the official name?

@davidmpickett
Copy link
Contributor Author

@thejordanwood The expected behaviors for Vet Centers are spelled out fully in the parent epic but essentially, all instances should show both names.

When a Vet Center with both an official and common name is included as a nearby location for another Vet Center, or in Facility Locator search results, both the official and common name are displayed.

@davidmpickett
Copy link
Contributor Author

@thejordanwood @xiongjaneg This seems pretty refined now, thoughts about moving to Ready? Or do we want to review in UX Sync tomorrow?

@xiongjaneg
Copy link
Contributor

@davidmpickett I'm OK to move to Ready if @thejordanwood is.

@thejordanwood thejordanwood self-assigned this Oct 26, 2023
@thejordanwood
Copy link

@davidmpickett @xiongjaneg This has been moved to Ready!

@aklausmeier
Copy link

@thejordanwood reviewed, looks good, checked off AC for my review

@thejordanwood
Copy link

Last week, I created mockups in this Sketch file to show how facilities can display complex names consistently across the site.

I started a slack thread to get feedback.

@xiongjaneg xiongjaneg mentioned this issue Nov 22, 2023
16 tasks
@xiongjaneg
Copy link
Contributor

review schedule for 11/30 UX sync

@jilladams
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide UX Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

5 participants