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:
@Agile6MSkinner @jilladams
IA point of contact:
@kristinoletmuskat
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?
[x] Yes - Please note: Redirect still needs approval from IA.
Thanks, @kristinoletmuskat ! This is actually a Facilities one, so I'm pinging @Agile6MSkinner and changing the tag from Public Websites to Facilities .
Instructions
Type of request
Do you have a product technical team able to implement this redirect?
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:
Redirects
And all child pages, and variants of capitalization Use
catchAll
for allThese are page level redirects for a Teamsite using the injected header -- it can be done within proxy rewrite as a client-side redirect
Link to campaign landing page request issue, if relevant:
Process, Roles and Responsibilities