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

Drupal Design: Update Vet Centers to reflect front end changes #18125

Open
4 tasks
thejordanwood opened this issue May 15, 2024 · 1 comment
Open
4 tasks

Drupal Design: Update Vet Centers to reflect front end changes #18125

thejordanwood opened this issue May 15, 2024 · 1 comment
Assignees
Labels
Blocked Issues that are blocked on factors other than blocking issues. Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status UX Vet Center CMS managed product owned by Facilities team

Comments

@thejordanwood
Copy link

thejordanwood commented May 15, 2024

Description

For the Vet Center 2.0 initiative, front end designs are being updated to solve problems that relate to Vet Center branding, events, and satellite locations. After the FE designs are finalized, Drupal changes will need to be made to accommodate these updates.

Design

Vet Center Figma file

Drupal Considerations

Consider how these changes will impact Drupal.

Changes from #17891:

  • Adding the Vet Centers logo to the top of the page The logo will likely be hard-coded into the FE template rather than handled via Drupal - @davidmpickett
  • Adding a summary box to the top of the page that describes what Vet Centers do
  • Moving the "How we're different than a clinic" section below the contact info
    • Move position of FAQ on [Vet Center Centralized Content]? Not be a functional necessity for updating the FE template
    • Update position on Node View and Node edit for Vet Center nodes for local editor awareness?
  • Changing the "Referral services" to "Recommendation services" or something similar. A final decision can be made on this later.

Changes from #18121 :
TBD

Acceptance Criteria

  • Design are documented in Figma
  • Review with UX Lead, Product, Engineering, Content, and Accessibility
  • Design is reviewed with and sent to VA UX Lead for final sign off
  • Follow up tickets are created
@thejordanwood thejordanwood added Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Vet Center CMS managed product owned by Facilities team UX labels May 15, 2024
@thejordanwood thejordanwood self-assigned this May 15, 2024
@davidmpickett davidmpickett added the Blocked Issues that are blocked on factors other than blocking issues. label May 15, 2024
@davidmpickett
Copy link
Contributor

@thejordanwood - thanks for getting this started. I totally misunderstood what you meant when you said you'd create the Drupal ticket yesterday. Thought you meant an implementation ticket for Drupal engineers 😂

It's really smart to be tracking related Drupal updates here as you work through the FE tickets. I added some comments and sub-items about different parts of Drupal that we'll have to look at for these various elements

@davidmpickett davidmpickett changed the title Design: Update Vet Centers in Drupal to reflect front end changes Drupal Design: Update Vet Centers to reflect front end changes May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked Issues that are blocked on factors other than blocking issues. Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status UX Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

2 participants