-
Notifications
You must be signed in to change notification settings - Fork 70
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
Update Service Location paragraph type to account for VBA #14704
Comments
@xiongjaneg we need to cut a follow up ticket to put in the backlog for exposing these fields and change management, when the time comes. |
|
@xiongjaneg I want to confirm that this is the design we're talking about reviewing in in the first AC: https://www.sketch.com/s/891d33ae-152d-471c-ab5d-9aedf89cf6ff/p/FC995695-308A-4493-8461-D9AFE6DC6B25/canvas |
@thejordanwood Can you confirm the Sketch link Christian is referring to is the most recent? Thank you! |
@xiongjaneg @omahane This is the Figma file that will have the Service location paragraph type. It's a bit confusing, but CMS designs are in Figma and front end designs are in Sketch. I just commented on my Service locations ticket and pointed out that, while I've done some UX review of this, I haven't completed the work yet. I'm missing some of the suggestions in Dave's spreadsheet. Specifically the suggestion for better help text to describe what Service Locations are and the addition of the delivery method field. I'm now realizing that perhaps I should have completed that ticket first, before completing work for Service Regions and other content types that contain the Service Location section. |
@omahane Do you have what you need to continue work on this? |
@xiongjaneg @thejordanwood @davidmpickett Can I get some clarity on the title? Is this something that an editor is going to manually create/edit? Other facility service titles are generated: Patterns for service titlesVet Center Service title
VAMC System Health service title
VAMC Facility Health service title
|
The other thing I want to confirm is that, aside from title (which I've asked about above), the only net new field is "Service description." Otherwise, it's mostly help text changes/additions. Is that right, @thejordanwood ? |
The most recent FE design to review is probably the annotated Service accordion: |
No. There are at least 4 net new fields:
This is what I was referring to when I mentioned the spec was wildly out of date |
This is a good question, but it's not technically part of Service Location, right? It's something that should be addressed on VBA Facility Service? |
You're so right, Dave. I was totally conflating the two, having looked at the Figma file from here: #14704 (comment) |
Per Slack conversation with DaveP, we'll be handing the Appointments structure in #14837, rather than doing so here. |
@omahane can you confirm the state of this ticket? Not all ACs are checked, and not sure ifyou need an assist with anything since Jane is gone? |
The accessibility review AC is going to have to wait until we've gotten sign-off from @mmiddaugh that our free text fields are the right approach. |
Remaining AC moved to #15649 closing! |
Description
Drupal implementation for VBA Service Location paragraph type is built to match the spec #13128. (Note from Dave - the spec has not been updated to reflect the FE design, so it is wildly out of date)
Collaborate with DaveP if questions arise based on the spec during implementation.
Change management notes
We want to add new VBA fields to Service Location, but do not want those fields to be visible in Prod to VAMC editors yet. That requires Change Management. #14758
Acceptance Criteria
The text was updated successfully, but these errors were encountered: