-
Notifications
You must be signed in to change notification settings - Fork 201
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 and remove VRRAP content—HOLD TO PUBLISH UNTIL 12/11/22 #49766
Comments
Noting here that we also have VRRAP content on the COVID FAQs page in the question "If I lost my job due to COVID-19, can I get education or job training from VA?" that needs to be changed. |
On Other education benefits, I removed the VRRAP content and added an info alert to the top of the page — we chatted with Joni about using an info alert so that this is near the top of the page when folks get redirected from VRRAP page. We can leave this up for 6 months and then remove. http://preview-prod.vfs.va.gov/preview?nodeId=945 @RLHecht since Megan is busy with rates, want to review the info alert? That way we can get this off to stakeholders. Also noting that 12/11 is a Sunday, so we'll need to ask if it's okay to publish Monday morning 12/12. Question: How does this work with redirect timing, since that's not immediate? And for the Covid FAQ, Danielle confirmed we can simply remove the VRRAP question — I updated the node: |
Update: Laura sent content to stakeholders on 12/2. |
Terry approved this content and said Monday is fine — we just need to confirm timing of the redirect. @megzehn these are ready for copyedit/pre-pub ahead of publishing (likely first thing Monday morning):
|
Hey @megzehn , new plan here. Since the program closes Sunday but the redirects won't happen until Monday morning, we're going to update the pages with a future-tense alert this afternoon. Then we'll update the alert to past tense on Monday morning. This also means that we'll place the alert on the VRRAP page itself until the redirect is live and we can archive that page. Here are the updated pages ready for copyedit/prepub:
|
Hi @megzehn , Terry approved this new plan — you can go ahead and publish these updates. On Monday morning, I'll adjust the alert with the past tense version and tag you to republish. |
Thanks, @laurwill! I reviewed and published these! |
Hi @megzehn , I updated the VRRAP alert to past tense — could you review and publish? I don't think we need to wait for the redirect to take effect, since it should be past tense now no matter where it's appearing. We'll also need to remove VRRAP from the left nav. Want to do that at the same time as you publish the alert? Let me know if you want second eyes on the left nav change! |
Hi @laurwill, I republished the updated alerts and removed VRRAP from the left nav. Thanks for doing this work! I also just confirmed that the updated alert is on the live site, and I'm not seeing VRRAP on the left nav. |
Amazing! I notified the stakeholder. @RLHecht I'm going to go ahead and close this since you're OOO, but noting that for your tracking purposes. |
Issue Description
The VRRAP program will stop accepting new applicants on December 11, 2022. The education team opened an intake request to have us remove all mentions of Form 22-S900 and VRRAP information on various VA pages and to retire the Veteran Rapid Retraining Assistance Program page.
Original intake ticket: #49776
To remove:
We should assess whether we need messaging on the other VA education benefits landing page about the program ending. It may be confusing if someone is looking for it and it's no longer there.
We also need the CMS team to do an audit of VA.gov to learn if VRRAP is mentioned on any other pages. And we need to reach out to Tammy Hurley to remove the mentions on the school administrators page.
We will need to also set up a redirect for the page we're retiring and determine what we should be redirecting to. @heyjoni will help us with this.
Note that none of these changes can go live until 12/11/22.
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: