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

Continue to update police transparency design to account for expanded contact information #17343

Open
4 tasks
thejordanwood opened this issue Feb 26, 2024 · 3 comments
Assignees
Labels
Blocked Issues that are blocked on factors other than blocking issues. Facilities Facilities products (VAMC, Vet Center, etc) points-5 sitewide UX VAMC police transparency Sub-product of VAMC VAMC CMS managed product owned by Facilities team

Comments

@thejordanwood
Copy link

User Story or Problem Statement

Use the designs from VAMC non-clinical pages in #17342 to create a design to show expanded contact info on police pages.

In #16415, it was decided that we will be moving to a model where local editors can associate multiple blocks of contact information with their VAMC System VA Police Page. Our current design only has room for a single phone number in the middle of a paragraph.

Some work has been started on this in #16810.

Design

Expand Contact Info page in the Police Transparency Figma file

Acceptance Criteria

  • Document recommendation for designs in Figma
  • Requires content design review
  • Requires accessibility review
  • Requires UX/UI Lead review
@jilladams
Copy link
Contributor

Holding for now as we are waiting for PAO's to provide more information before we dive in here.

@jilladams jilladams added VAMC CMS managed product owned by Facilities team VAMC police transparency Sub-product of VAMC labels Mar 27, 2024
@jilladams jilladams added the Blocked Issues that are blocked on factors other than blocking issues. label Mar 27, 2024
@mmiddaugh
Copy link
Contributor

mmiddaugh commented Mar 27, 2024

@thejordanwood @aklausmeier
Here is my tentative list of questions for PAOs. Please let me know if I am missing anything which would be important to your design approach.

  • Beyond non-emergency phone numbers (which we already have), do you need to display additional contact information at the system level?
    • If so, what kind (address/phone/email)?
    • One or more?
  • Do you need to display specific contact information at the facility level which is different than the system level contact information (mentioned above)?
    • If so, what kind (address/phone/email)?
    • If so, is this a need for every facility within the system? (or just VAMCs? Or just a subgroup of the facilities?)
    • One or more?

My plan would be to get these answers plus any available examples

Also tagging @davidmpickett as it may relate to content modeling

@davidmpickett
Copy link
Contributor

Those look good. Some additional questions to try to drill into whether Service Location cardinality can be capped at 1

For facility level information:

  • Is there a typically a single location/office within a facility where in-person police services are offered?
  • Are there ever situations where Veterans might need to go to one office for some police-related tasks (e.g. lost and found) and a separate office within the same facility for other tasks (e.g. reporting an incident)

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. Facilities Facilities products (VAMC, Vet Center, etc) points-5 sitewide UX VAMC police transparency Sub-product of VAMC VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

5 participants