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

Finalize design recommendations for duplicate content in service locations #17751

Open
5 tasks
thejordanwood opened this issue Apr 4, 2024 · 0 comments
Open
5 tasks
Assignees
Labels
Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) points-5 sitewide UX VAMC CMS managed product owned by Facilities team

Comments

@thejordanwood
Copy link

Description

VAMC service locations have duplicate content. Recommendations need to be made that show solutions to this problem and help reduce the amount of duplicate content. This work was started in #17342.

Use Cases

  1. Duplicate mental health numbers, ticket #17397
  2. Same number showing multiple times, ticket #17251
  3. Duplicate appointment phone number headers, ticket #17253
  4. Conditional validation for phone number labels, ticket #17425
  5. Duplicate hours

Acceptance Criteria

  • Document recommendations in Figma VAMC Master file
  • Review with content designer
  • Review with accessibility
  • Review with UX Lead
  • Update engineering tickets with specific updates
@thejordanwood thejordanwood added Facilities Facilities products (VAMC, Vet Center, etc) Public Websites Scrum team in the Sitewide crew labels Apr 4, 2024
@thejordanwood thejordanwood self-assigned this Apr 4, 2024
@thejordanwood thejordanwood added VAMC CMS managed product owned by Facilities team Design CMS team practice area UX and removed Public Websites Scrum team in the Sitewide crew labels Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) points-5 sitewide UX VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

2 participants