Redirect Request for R&S article about EDU benefits and natural disasters

[bethpottsVADEPO]

Instructions

• Requests must be submitted AT LEAST 2 weeks in advance. Some requests take a significant amount of time and coordination to implement, so start the process as soon as you know you will need one.
• This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.
• It is your responsibility to notify VA stakeholders as appropriate.

POC	Github alias(es)
Product team point(s) of contact:	bethpottsVADEPO
Content point of contact:	bethpottsVADEPO
IA point of contact:	IA will enter

Type of request

• [x] We are retiring or taking down a page and need to redirect the URL (complete redirect section)
• [ ] We are changing the URL of an existing page (complete redirect section)
• [ ] We need a custom vanity URL (complete vanity URL section)
• [ ] We are removing a temporary redirect (add relevant background and link to original redirect request)

Do you have a product technical team able to implement this redirect?

• [ ] Yes - Please note: Redirect still needs approval from IA.
  • [ ] Please verify your team has reviewed Redirect governance and Redirect technical implementation information
• [x] No - CAIA will need to make Public Websites aware of the ticket.

Implementation date

When does this request need to be live? NOTE: Redirects in vsp-platform-revproxy auto-deploy M-Th. Friday launches should be avoided. Choose one:

• [ ] On a specific date, connected to a program or publishing requirement. DATE:
• [ ] Any day prior to a deadline/latest possible date. DEADLINE:
• [ ] Any day after an earliest possible date. EARLIEST DATE:
• [x] During a specific date range: EARLIEST DATE TO LATEST DATE: 10-15 (today) - 10-18 (if possible, since we now have more up-to-date info available in the new disaster help article)
• [ ] No hard timing requirements, publish when possible.

Redirects

Current URL	Redirect Destination or New URL
https://www.va.gov/resources/what-if-my-school-closes-temporarily-because-of-a-natural-disaster/	https://www.va.gov/resources/disaster-help/

Vanity URLs

Vanity URL	Landing page
requested URL	landing page URL

Link to campaign landing page request issue, if relevant:

Process, Roles and Responsibilities

• [x] Requesting team: Above information is provided
• [x] Requesting team: All appropriate VA stakeholders are notified as appropriate
• [x] IA: Request is vetted and documented and implementation plan is clear
• [x] IA: Request is assigned to appropriate team for implementation
• [x] Implementation team: Work is complete
• [x] Implementation team: Validated in production
• [x] Requesting team: Validates everything is correct in production and closes ticket

[scjwalker]

Requested URLs reviewed by IA - everything looks good. Checking with Beth in Slack about notifying stakeholders.

[scjwalker]

@FranECross This one's ready for the PW team.

[scjwalker]

Beth confirmed on slack that stakeholders have already been notified.

[FranECross]

@scjwalker Will you please provide the redirect URLs? Thanks! The ticket indicates a preferred implementation of today, but this hasn't been refined and our sprint has already started. Do you and stakeholders wish this to be an injection, since it has to do with natural disasters? Thanks! cc @jilladams

[bethpottsVADEPO]

@FranECross Redirect this page: https://www.va.gov/resources/what-if-my-school-closes-temporarily-because-of-a-natural-disaster/ To this page: https://www.va.gov/resources/disaster-help/

Can this be worked into your sprint (doesn't have to happen today)?

[FranECross]

@bethpottsVADEPO Thanks for that info! Yes, I'll pull it in for early next week and let the team know.

[FranECross]

Notified the FE engineers via Slack about this item, and requested a Monday implementation (which will probably then release on Tuesday after 10 am). https://dsva.slack.com/archives/C52CL1PKQ/p1729277794591719

[jilladams]

Chris is out today but has a PR up. I've nudged it to see if we can get approvals. We'll make a note here once it merges, to let you all know timing for deployment.

[randimays]

Code has merged. The redirect can be validated in production shortly after 9am CST tomorrow morning.

[scjwalker]

I just checked - the redirect is working as intended. Once the other checkboxes are done I'll validate and close the ticket.

[jilladams]

@scjwalker double checking which checkboxes? I think the work for this ticket is done from Sitewide's side, but want to make sure we aren't overlooking a list somewhere that I'm not seeing.

[scjwalker]

@jilladams The ones for the implementation team. Looks like they're checked now!