Update to static pages for burial allowance form re-launch

[aliyahblackmore]

Issue description

Ahead of the MVP re-launch of the new 530 EZ online form questions, we need to make updates to the How to apply for a VA burial allowance page to align with the new form questions. Here's a link to their launch plan

For MVP we're only making updates to the static page that relate to missing information from the form or the changes that they made to the form.

We'll make these updates:

• In the section "Is there a time limit for filing?" we'll update that section with information about the time limit for unclaimed remains.
• In the section "What documents do I need to send with my application" we'll update the content to align with the updated information on the form intro page.
• And we'll also need an info alert, similar to the pension static page, that let's users know that there are updates on the form and new questions.

And we also need to add the online form option the About VA forms page.

Since this form is launching incrementally, we'll need to have the the product team add two versions of the content in a react widget. This is their ticket for these updates.

---

Tasks

• [x] Draft content
• [x] Share with SMEs (Aliyah)
• [x] Share two versions of content with engineer for incremental launch (A)
• [x] Review widget content with Engineer before PR merge
• [x] Add widget to page (Aliyah)
• [x] Review with engineer, copy edit and publish for incremental launch (Megan)
• [x] Ahead of 100% launch, add content (version 2) to page and delete widget.
• [x] Copy edit and publish (Megan)
• [x] Share with SMEs

[aliyahblackmore]

Update here:

I shared the static page updates with their SMEs (via Teams) a few minutes ago. Here's a link to the SharePoint document that SMEs reviewed

Once SMEs confirm we the updates, I'll share the content with their engineer so that they can create a widget for the incremental launch.

[aliyahblackmore]

• SMEs reviewed the content for the How to apply page and I’m creating a SharePoint document with the two versions of the content to share with the engineers this week (insert link when ready).
• While I'm OOO - A will have Megan review the widget copy and then they can share the SharePoint document with their team in this ticket and tag Dakota.
• A can add the widgets to the page, if it’s ready before next Monday. And A and Megan can have the engineer toggle it on to do a review.

[aliyahblackmore]

@aprocik1 thanks for the coverage while I'm OOO.

As we chatted, SMEs reviewed these updates to the How to apply for a burial allowance page ahead of the incremental launch.

Here's the SharePoint document

And here's an exported Word document version, in case there are any issues with SharePoint. React widget content for “How to apply for burial allowance_word export_3.19.docx

• After you have Megan review this content, you can share the document with the engineer on the 530 product team in this ticket.

• In terms of how the widget should work, as I mentioned, I believe the engineer has to decide whether the page will require multiple widgets or one widget. Can you confirm this with him?

• If the engineer decides to use one widget and wants to place all of the content there, you'll just need to copy the current page content between "Am I eligible..." and "How do I apply?" For the version that will be visible for users who can see/use the updated form, you can just insert the new content and leave the other content as is.

[aprocik1]

@megzehn, can you copyedit this SharePoint document?

The first 3.5 pages under the header "Content for the users who can see the online form" will go into react widgets on the How to apply for a Veterans burial allowance page. The remaining pages under the header "Content for the users who can’t see the online form" should be the same content that's already on the published page.

The engineer asked for this SharePoint document by the end of this week. Please let me know if you don't have time to copyedit it by then. Thanks!

[megzehn]

Thanks @aprocik1 and Aliyah!

I made some light copy edits in this Sharepoint doc.

Let me know if there are any problems accessing the doc or questions about the tweaks.

[aprocik1]

Thanks, @megzehn! I accepted your suggested edits and shared this document with the engineer to build the react widget(s).

[aliyahblackmore]

Thank you both! @aprocik1 @megzehn

Tracking here that I followed up with their engineer about when they'll have the code ready. Once we have the code in Drupal, engineer will toggle on so that Megan can do a review.

[aliyahblackmore]

Update here:

• Engineer shared a link to the PR for this widget. This is the widget code: burials-v2-how-do-i-apply-widget
• We met today to review and widget and he's going to make some adjustments to the widget copy to reflect the pieces of content in between the areas we updated.
• Engineer will follow up about the current widget on the page for the form link.

[aliyahblackmore]

Updates here:

• Engineer will make a few more style updates to react widget content and I'll take another quick look. I have some time tomorrow, in the early afternoon or on Monday.
• Our copy editor will do the toggle on/off review once the widget code is ready and in Drupal.
• Engineer mentioned that he'll push the content changes production (changes won't be visible on VA.gov until we published the page with the widget code).
• Engineer confirmed that we CAN remove the "burial-apps-status" widget that's currently on the page and we can use the direct link to the form intro page for the action link "Apply for burial benefits."

• Incremental launch date is still TBD.

  Once I add the widget to the page, I'll need to make "What if I have more questions" a separate Page Specific Q&A group.

Last communication with team was on 3/28.

[aliyahblackmore]

Updates here:

• If the incremental launch date changes (currently April 5, 2024), engineer will update the day.
• Engineer will get the PR merged (content that they put in the code)
• Once the PR is merged, we can add the code to our react widget component in Drupal
• A copy editor will reach out a day or two before the incremental launch to do the toggle on/off review

Once the form is at 100% and we and the react widget content to the Drupal page, we can adjust the info alert date (mural has May 1 as the 100% launch date).

Last communication with engineer was 3/29.

[aliyahblackmore]

Hi @megzehn - welcome back!

A and I did one review with the engineer of both versions of the content and noted some updates to the widget version. And then I did a second review with their engineer after he made the changes.

The engineer shared the widget code with me and I added it to Drupal today. I just noted one last change about the spacing between the "Note" and header in the featured content box. Outside of that, everything else look good.

Do you have some time this week to do that flipper toggle on/off review with him so that you can look at the content that users who can use the online form will see?

Here's the content doc for reference

Let me know and I can connect you with their engineer!

[aliyahblackmore]

Tracking some updates here after syncing with Megan and chatting more with engineer this afternoon.

Resharing their teams release plan And Mural document in timelines

Notes on who may get V2 of the form during incremental launch:

• Dakota just confirmed that only auth users will get the see the new version (V2) of the form during the incremental launch. (TBD if auth users with V1 saved in progress forms may see V2 during the incremental launch).
• My understanding is that the two versions of the content on the static page still work. This is because auth users will be the users who CAN see the new version of the form and unauth users will be the users who CAN'T see the new version of the form. Let me know if that sounds right to you.

Info alert under "How do I apply" and auth users with saved and in-progress forms:

• Dakota mentioned that auth users with saved and in-progress forms may get to use V2 during the incremental launch, if so we can leave the info alert. If the form will only be for auth users who are starting a new form, we could remove the info alert on the static page. But we could also leave it on because the How to apply for a pension benefits page has a similar alert for auth and unauth users at various stages of applying. I asked Megan to follow up with thoughts on this.

Question for Dakota:

• Since the incremental launch will be for auth users only, is there anything that we need to do or is that feature controlled by you all once we have the widget on our page?
• Some auth users may see the new version of the form and the new content on the static page and some won't -- the content on the page looks the same for auth and unauth users. I signed in with a test users account in staging and looked at the How to apply for health care and How to apply for pension benefits pages and the auth and unauth versions are the same.

[aliyahblackmore]

Updates here:

• Megan and I met with Dakota last week and requested one last style update to the featured content box.
• Dakota made the update.
• Canary testing will start on April 15. Megan will publish the page (with the react widget) then.

[aliyahblackmore]

Updates here:

• The react widget is already in Drupal and ready for @megzehn
• @megzehn will coordinate publishing with the product team on Monday

Last communication with team was on 4/12.

[aliyahblackmore]

Update here:

• SMEs need to approve updates to the "What documents do I need to submit?" section. Laura Steele confirmed on 4/29 that these updates are okay to go ut post-100%. If this plan changes and updates need to happen this week, Dakota will need to add these updates to the react widget.

This is the SharePoint document I shared with SMEs This is the SharePoint document from Megan/A with the react widget content for users who CAN use the V2 online form.

If SMES have any feedback on the updated section, track updates ^ here and share with Dakota. And coordinate publishing timing with the form updates, because the form intro page now links out to the static page with more details about the types of supporting documents. Also, be aware that the react widget content is already in production - coordinate deployment timing with engineer because update will show once the deployment happens.

[aliyahblackmore]

@megzehn

HOLD TO PUBLISH until the team confirms 100%. Laura S. flagged (5/14) that there's an issue the team is working on and 100% likely will be during the week of 5/20.

How to apply for a burial allowance page is ready to be re-published for the 100% launch. Preview link: https://preview-prod.vfs.va.gov/preview?nodeId=864

• I removed the react widget from the page **The info alert is the new piece of content that wasn't in the react widget
• We also got new information from SMEs last week and death certificates aren't required in the form flow if someone is claiming an allowance for a service-connected death AND the Veteran's death happened at a location that isn't a VA medical center. To address this in Drupal, I added "may" in the sentence "You may need to provide..." SMEs approved this. If we can't publish at the same time that the form goes to 100%, the product team already planned to have content in place in the form for users who have saved and in-progress forms (link to Figma screen) And we'll need to re-publish this page in the future after we get SME approval on future enhancements to the for flow.

About form page is ready to be re-published for the 100% launch. Preview link: https://preview-prod.vfs.va.gov/preview?nodeId=39934

• I added the online form link to the page.

[aliyahblackmore]

Update:

We received new information from SMEs today about death certificates and service-connected deaths. We may need additional adjustments to this page before 100%.

[megzehn]

Yay thank you @aliyahblackmore!

Confirming I reviewed your changes and published them once the team confirmed they were at 100%

I also published the update to the form detail page!