Closed davidmpickett closed 1 year ago
These notes are for mostly future reference for @BlakeOrgan and @thejordanwood when we get into the nitty gritty of interface design for Service Locations in future tickets.
This is an example from Drupal of a VAMC Facility Service with 2 Service Locations.
^ There should be some better visual indication that these are two distinct Service Locations that can be rearranged. At minimum possibly a header that says "Service Location" for each instance plus the draggable four way arrow icon.
Compare this to the pattern we're using for Q&A sections where each Q&A in the Questions Section is clearly labelled.
Currently when a Content Type uses the Service Location Paragraph Type, there is no help text that comes with to describe the overall Service Location interface, that has to be added per Content Type. For example in VAMC Facility Non-clinical Service this Service Locations section has no help text intro.
Whereas VAMC Facility Service has a header and a block of text that introduces it nicely.
Possible path forward? Create a new Appointments Paragraph Type modeled after this part of the VAMC Facility Health Service:
I think this draft is as good as i can get it with out chatting more with the team
A single field in this Paragraph Type required a whole new section of the mural
Meeting recording from Facilities team review https://civicactions.zoom.us/rec/share/wXdNXmzKdlFl2eGo-d4eajLxh0h_3LLR_BXGjggQVZx-5q4urKsLZZQ8vMOIYsNj.aFKRJt2MyJtbpCWo?startTime=1682361146000 Passcode: *j89Kk@C
To iterate on before CMS collab cycle:
Description
AS A Drupal engineer, I WANT a technical design document of the Service Location paragraph type SO THAT there is nothing ambiguous about the implementation requirements.
AS A PO, CMS team member or stakeholder I WANT to see a detailed content spec SO THAT I can review the design before implementation
Example artifact
Acceptance Criteria