Website updates

Applications Pidgin
1

We’re starting to prepare for updating the site for pidgin3.. but obviously we don’t want to break all the links (again).

My proposed solution right now is to re-root the existing site to /2 and redirect pidgin.im/[^2]* to pidgin.im/2$1. Then we can start building/deploying the 3.0 site at /3 and at when we’re ready, redirect / to /3.

I’m not sure if the pidgin2 windows installer will work with this, but i believe we’ve already worked around that with a previous redirect. I need to double check this.

Can anyone think of any issues with this setup?

2

Won’t this break the old links once you redirect to /3 or do you plan to have each page that exists now available on the 3.0 site?

3

I probably wasn’t clear enough…

The more technical plan is

/ (no wildcard) redirects to /2 with a HTTP 307 (temporary) redirect.

Then everything that doesn’t start with /2* or /3* and push it to /2 with a HTTP 308 (permanent) redirect.

When we want to make /3 the default, we change the / redirect to /3 and keep it an HTTP 307 (temporary) for the eventual /4.

/3 and the eventual /4 and so on won’t need redirects because they’ll have their own custom path which won’t break links in the future.