Closed JessicaMarine1 closed 1 year ago
@brentryanjohnson are there specific URLs we wanted to re-direct?
@A-L33 ^^^
I'll work on this next (after accessibility testing).
Ideally, we would be able map chunks of redirects based on a hook in the existing paths, but most of the pages on the current site are in a /content/
subdirectory, so they aren't currently organized by path.
I think we can start by using the content docs the team created, which contain the current URLs for the pages that were rewritten and consolidated. Those should represent the most highly accessed pages, and I can map those to the new URL paths.
@brentryanjohnson Would it be possible to build a mapping of old pages to new from the content audit? With Astro, we can give it a list of old URLs and their respective new URLs, and it'll handle the rest.
Yep! That's what I'm working on. I don't think we need to map everything over, but I'm crosswalking the pages we moved and consolidated to their origin.
Here's a first attempt to map paths for redirects. @A-L33 Can you take a look and make sure nothing (important) is missing?
This approach doesn't contemplate redirecting every page (that is, it doesn't identify an individual page redirect for every existing page). If we need to go larger scale with redirects, we can, but we might want to take some time to think through which pages make sense. Outside of these specific page-level redirects, all other URLs would redirect to the new homepage.
The formatting of those ☝️ got a little funky, so you might want to view them in sheet 2 of the 🔒 IA google sheet
I'll review with @rebekahperillo and get back to you!
@brentryanjohnson Would it be a huge pain to put in a redirect to the current individual state pages to the landing page of state taxes in the new website? Something like this: https://smartpay.gsa.gov/statetax/florida -> either https://federalist-ab31a10d-375d-4040-9324-1ae94e8a36b9.sites.pages.cloud.gov/site/gsa/smartpay-website/smarttax/state-tax-forms/ or https://federalist-ab31a10d-375d-4040-9324-1ae94e8a36b9.sites.pages.cloud.gov/site/gsa/smartpay-website/smarttax/state-tax-forms/florida/?
If anyone is going to bookmark a state, they're going to come in through a search engine. Just a thought.
@brentryanjohnson Can we add https://smartpay.gsa.gov/glossary -> Master Contract? Thank you!
Yep! It's kind of difficult to see, but the table includes https://smartpay.gsa.gove/statetax/[state]
-->smarttax/state-tax-forms
I'll add the glossary redirecting to Master Contract!
Thank you Ryan! I'm good here @rebekahperillo if you are.
@A-L33 Trusting your work here. Good to go. :) Thank you!
@brentryanjohnson I was able to implement most of these so far, but added comments to the IA sheet where I need clarification on a few rows. Could you take a look whenever you have a chance? No rush, because I also have the accessibility changes to implement in the meantime.
@jfredrickson5 I replied in the sheet!
@brentryanjohnson Jeff indicated that this should be done. Can you please review before we send to POs?
I corrected some destination paths in #285. It should be ready for review once that branch is merged in.
@A-L33 @rebekahperillo this is ready for review. @brentryanjohnson any suggestions how they might review this?
@A-L33 @rebekahperillo We won't really be able to test this until we're in production, since the redirects won't be active until there is no longer a viable link for a current page (that is, until the current https://smartpay.gsa.gov/content/about-gsa-smartpay becomes the new smartpay.gsa.gov/about
– which isn't a live URL yet!).
In the meantime, the logic that will ultimately drive redirects is in this file →.
Beyond the first few lines, you'll see "key:value" pairs. Basically, one URL path, then a comma, then another URL path.
"/content/about-gsa-smartpay": "/about",
"/gsa-smartpay-benefits": "/about/benefits",
The first path will be the page on the current site. Then a comma, followed by the new page we're building.
These should look like what you reviewed in a previous comment ☝️, but this is the code version that will drive the actual redirects. 👍
Let me know if you have any questions!
Maybe we move it (or add a new issue) to post-MVP and test once we're live. We have a similar issue with DAP.
Moving to done! Opened issue #292 for post-launch check.
You can sort of test this currently by tacking on the "from" redirect to the preview URL, like this:
Take the base preview URL, which is:
And add, for example, content/about-gsa-smartpay
(which is this page on the existing site) to the end of it, to get:
And if you follow that link, it should redirect you to the new About page at:
Hope this helps!
@rebekahperillo I added these to a 🔒 new google sheet and activated the (legacy) link paths to try to make it easier for you to test them 👍.
You are awesome. Thank you!
As a user of the legacy system, I need any existing bookmark/link to still work, so that I can still easily access the new site.
Many users of the legacy system likely have bookmarks / links saved. We should ensure folks' bookmarks/links still work (e.g., by using redirects), or provide a workaround if we change the page URLs they're familiar with (e.g., have the 404 error page list the top requested content pages).
Acceptance Criteria: