Skip to content
This repository has been archived by the owner on May 26, 2023. It is now read-only.

Redirecting everything to new site #126

Closed
wants to merge 1 commit into from
Closed

Redirecting everything to new site #126

wants to merge 1 commit into from

Conversation

JamesBelchamber
Copy link
Contributor

This will turn every page into a redirect to https://www.fedoraproject.org/silverblue

Bit hacky, but it's simple and it'll work while we put in a proper 301.

@nikodunk
Copy link

nikodunk commented May 23, 2023

Hi! Wouldn't it be better to leave this as-is and file an issue on https://pagure.io/fedora-infrastructure/issues to reroute silverblue.fedoraproject.org to fedoraproject.org/silverblue?

@JamesBelchamber
Copy link
Contributor Author

IMO we should do both - this PR will get the redirect in place now, while the infrastructure team implement a 301.

The redirect I've used is a pretty standard one that's accepted by search engines as equivalent to a 301, too. So, starts building up that re-indexing :)

@JamesBelchamber
Copy link
Contributor Author

Ticket raised with the Fedora Infrastructure Team here.

@travier
Copy link
Member

travier commented May 24, 2023

I'd say that we are not in a rush to move. Let's wait until the redirection is in place in the Fedora infra for a week, and then we'll just decommission the old website and archive this repo. This keeps things neatly working and ready if for whatever reason something happens.

@JamesBelchamber
Copy link
Contributor Author

Having two websites can be confusing for users, and if there are any delays (e.g. while the infrastructure team confirm a request, or try to identify where the config is, or.. whatever) then this confusion could extend beyond a small window. This PR neatly ties up this loose end.

On the flip-side, there's no real advantage to leaving the site up as it stands - reverting the change would take minutes, and anyway, the move has been "decided" in practice (since the change has already been made to the main website). The website content is archived (in this repository) so there's no loss there either.

I think this also underlines the need for a SIG - let's decide how to do the changeover in advance, and externalise those decisions, so people can contribute well :)

@JamesBelchamber
Copy link
Contributor Author

The redirect is now set up on the infrastructure side, closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants