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

Implement UX recommendations to Service Location Address paragraph type #17488

Open
22 tasks
davidmpickett opened this issue Mar 11, 2024 · 2 comments
Open
22 tasks
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) points-8 Regional office CMS managed VBA product owned by the Facilities team sitewide VAMC CMS managed product owned by Facilities team

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Mar 11, 2024

User Story or Problem Statement

#14845 and #17342 both proposed updates to the Drupal interface for Service Location Address. Once the UX team has finished iterating, the final design should be implemented in Drupal

#17489 has the latest design decisions for this section.

This ticket will NOT address making fields conditionally required

Design

Location headers page in the VAMC Master Figma file.

Changes needed for both [same address] and [new address] scenarios:

"Street address" HTML element

  • Move field_use_facility_address and field_address out of this element
  • Remove this element

field_use_facility_address

  • Move this checkbox above other fields
  • Change checkbox label to "Same as facility address"

field_clinic_name

  • Change label to "Office or department name"
  • Update help text to "Add the name of the office or department within your facility that provides this service. This name should match physical signage at your facility to help Veterans find it."
  • While the design shows this field as required, that is NOT a change to make in this ticket. We have a separate ticket to discuss possible conditions under which it should be required: Consider: Conditionally require field_clinic_name on Service Location Address #17380

field_building_name_number

  • Add help text "Add a building name or number to help Veterans find the service location."

field_wing_floor_or_room_number

  • Add help text "Add a wing, floor, or room number to help Veterans find the service location."

[Same Address] Scenario

Changes needed when field_use_facility_address checkbox is selected

  • Display the facility street address
  • Add a "Facility street address" label above facility address

Address

[New Address] Scenario

Changes needed when field_use_facility_address checkbox is unselected

  • Display field_address subfields (country, street address, city, state, zip code) before field_clinic_name
  • Remove "Address" label above subfields

Address-1

Acceptance Criteria

  • Drupal interface for Service Location Address paragraph type matches design and changes specified above
  • Content types to confirm on
    • VAMC Facility Health Service
    • Service Region
    • VBA Facility Service
    • VAMC Facility Non-clinical Service
  • Requires design review
  • Requires accessibility review
  • KB articles and other documentation are updated? (product work?)
@davidmpickett davidmpickett added Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status labels Mar 11, 2024
@aklausmeier aklausmeier added the Blocked Issues that are blocked on factors other than blocking issues. label Mar 14, 2024
@aklausmeier
Copy link

blocked by design in #17489

@davidmpickett davidmpickett added VAMC CMS managed product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team and removed Blocked Issues that are blocked on factors other than blocking issues. labels Apr 17, 2024
@davidmpickett
Copy link
Contributor Author

Added to Team Refinement and UX Sync

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

No branches or pull requests

3 participants