Design Drupal Interfaces to support Vet Centers Outstation enhancements

[thejordanwood]

Blocked by #20212

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

• Parity between Node Edit and Node View?
• Dashboard experience
• Outstations
• Main location
• Locations page

Previous issues to address

• [CONSIDER] Improve Access point name help text in the absence of improved UX  #4903
• Vet Center satellite locations do not show their moderation state #6156
• Duplicate calls to action on Vet Centers Dashboard cards #10297
• New default introduction text from figma? [CONSIDER] Add default value to Page introduction for Vet Center VAST migration #4704
• Plain text links in Vet Center spotlights in CMS #10301

Suggestions from previous dashboard research

• Use a different label for "Link text" (e.g. Hyperlink) and reinforce the explanation with examples.
• Display information about when national content was last updated.
• Differentiate main VC from other locations.
• Add "scroll to top" functionality to the forms.
• Provide visual cue regarding content that was updated, but not saved.
• Adjust "Visitor information" label and/or be specific about what information is to be edited on this category.
• Make it clear that changing the operating status does not influence Location and Contact information information.
• Remove this information from the operating status flow or place Operating Status on its own block.
• Clarify what is there to edit when it comes to services at a VC.

Acceptance Criteria

• Proposal(s) for overall flow is documented and shared with Product and engineeer
• Designs are documented in Figma (as needed)
• Review with UX Lead, Product, Engineering, Content, and Accessibility
• Follow up tickets are created

[davidmpickett]

@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

[jilladams]

@thejordanwood (@Agile6MSkinner )I think we handled all these Drupal changes in other tix already and this ticket could theoretically be closed, unless we're trying to maintain Figma source of truth docs around Drupal UI?

[davidmpickett]

@jilladams That is true for the Vet Center differentiation Epic, but there will be more significant Drupal changes necessary for the Satellite Locations epic

[davidmpickett]

• Hey @davidmpickett take a look at [EPIC] Vet Center Editor Experience #4643 to see if any previously documented issues are still relevant and/od fixable as part of this redesign

[davidmpickett]

Considerations for the dashboard

• Visitor info, services, spotlight content, and operating status are all for the Main Vet Center
• Outstations don't stand out among satellite locations
• A vet center can have multiple outstations
• Outstations will also have visitor info, services, spotlight content, and operating status

[davidmpickett]

Make sure to address #10297

[davidmpickett]

Migrated old Dashboard designs to Figma file