-
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
FE: Add "Mission Explainer" / "Our commitment" Box to VetCenter Facility Pages #18724
Comments
Noting that we have a request out to the Design System team to update their guidance on On This Page component so we could exclude the blue box from having a jump link |
Noting that we do not have final content from CAIA. |
Added details on the CAIA blocker in ticket body. I bumped department-of-veterans-affairs/va.gov-team#83961 as well to see if they have updates, since we haven't heard anything this week. We are also blocked on product decision around timing / priority for building out Vet Centers 2.0 in content-build (and creating more drift for the AP template to catch up) vs. waiting for AP to ship, and building it all out in AP instead. |
I think we could do a quick estimate in refinement re: pulling fields through to FE in content-build, just to understand the lift, if we have time. |
@aklausmeier @laflannery Let's look at the DST ticket for exclude the explainer box from "One This Page" |
@eselkin Will do a bit of exploration on Graph QL and add to ticket. |
@Agile6MSkinner I have pinged the DST team for an update on an ETA for a fix to allowing exclusion of H2's from the On this page/ToC component |
A simple GraphQL query for vet centers is:
Returns something that looks like:
The If the Vet Center does not have fieldMissionExplainer, the whole object is null for example this query:
returns
|
@Agile6MSkinner There should be an AC/Task, (I'am not clear on the distinction tbh) to indicate that the summary box should follow all applicable annotations indicated here in Figma. Are you able to add that to the correct list above? |
@Agile6MSkinner The DST is expecting to allow the exclusion of H2s by December so we will need to pull that AC into it's own ticket as a follow-up when that is revised in the design system component. |
@omahane - Could this be related to the default value thing for Entity Fetch Fields? |
@davidmpickett Not sure, but if you go to the node's page on my tugboat or prod the mission explainer is in fact missing: |
@Agile6MSkinner could you add latest status here? OK for Eli to merge? |
Apologies, I thought I put the go-ahead here too. We can merge this @eselkin |
DO NOT MERGE until @Agile6MSkinner is notified for change management purposes
FINAL CONTENT FROM CAIA: department-of-veterans-affairs/va.gov-team#83961 Drupal functionality was created using Draft content. We do not want to publish that to the FE. Could build this and hold merge until final content is received, or opt not to work it yet.
User Story
As a veteran, beneficiary or caretaker, I would like to have a summary box displayed at the top of VetCenter facility pages so that I am quickly able to understand the mission and services offered for the facility I am looking at.
Description
Implement a GraphQL query to fetch VetCenter mission explainer content and use the existing "Summary Box" component from the design system to display it on the Vet Center pages.
Figma Designs
GraphQL recommendations from Eli
ACs:
Tasks
QA
The text was updated successfully, but these errors were encountered: