pages-core
pages-core copied to clipboard
cloud-gov
Support for 301 redirects
18F site would like to be able to redirect 18f.gsa.gov/feed/ to 18f.gsa.gov/feed.xml (the current Jekyll standard) with a HTTP redirect instead of a meta-refresh.
Why? Maintaining our audience as we migrate the site is important and not all devices will redirect RSS feeds with a meta-refresh. This will likely be important for many blogs using Federalist, so this update should be useful beyond this particular case. This is outlined in more detail in this issue.
Todo by 2022-01-20
- [ ] Have https://github.com/18f/pages-redirects repo be migrated to the cloud-gov org for Pages ownership.
When I had looked before it didn't look like there was support, but this stackoverflow thread has me thinking that I could actually solve this at the repo level after all
http://stackoverflow.com/questions/10178304/what-is-the-best-approach-for-redirection-of-old-pages-in-jekyll-and-github-page
We may want to look here for setting up redirects: https://github.com/18F/federalist-docker-build/blob/master/publish.sh#L31-L35
Here's the docs for that S3 configuration: http://docs.aws.amazon.com/cli/latest/reference/s3api/put-object.html
@lauraGgit brought up supporting redirects in the context of nicer URLs for single-page apps (so that an SPA doesn't have to use #-style addresses).
For reference, here's how Netlify allows users to specify custom redirects: https://www.netlify.com/docs/redirects/
Proxy supports redirects in https://github.com/cloud-gov/pages-proxy/pull/176. Next steps are identify a possible pricing model to support managing site redirects.
We will be migrating https://github.com/18f/pages-redirects into the cloud-gov GH org and begin the process of publishing the service offering.