Add old site contents for transition

[davelab6]

As part of #25 I got access to the old SF.net FTP area, and I see that it uses a .htaccess to redirect visitors to http://fontforge.org; so we can

• move the pages to here at the same URLs, so nothing breaks
• insert a message about the transition at the top of each old page, and
• merge this pr
• update the .htaccess on sf.net to redirect to http://fontforge.github.io instead
• ask Toby Thain to repoint the DNS A entry to Github's IPs
• when Toby confirms DNS is updated, change the CNAME to fontforge.org
• as each old site page's content is moved to a new site page, cut it down to a redirect

My initial message is,

This is part of the old website. New website begins at fontforge.github.io

Are you a web developer? Help us migrate this page on Github

[simi]

And why http://fontforge.org should not be used for http://fontforge.github.io/ also? Github pages supports custom domain also.

[davelab6]

I'll ask Toby Thain to re-point the DNS as soon as this is merged

[adrientetar]

I'm not sure it helps much to bring the old site verbatim, it's still available at sourceforge; the point of the new site is to have new content or updated one. Anyways.

GitHub Pages' not an Apache server, .htaccess is useless over here.

Does someone pay for fontforge.org?

[davelab6]

I'm not sure it helps much to bring the old site verbatim,

Until all the old content is moved over, I think it would be bad to just disappear the information off the web.

it's still available at sourceforge;

If we repoint fontforge.org to the new site, and the sf.net site has the .htaccess, then the old information will only be available buried deep in the git history....

the point of the new site is to have new content or updated one. Anyways.

Yes, and I think a good transition to get there is to have a single set of site files and migrate the content from old pages to new pages :)

GitHub Pages' not an Apache server, .htaccess is useless over here.

Yes, this is the file I'll push to the sf.net server

Does someone pay for fontforge.org?

Yes, Toby Thain in Australia

[adrientetar]

Well, merge it if it's ready to go.

[adrientetar]

Okay but right now upon accessing the new website you're redirected to the old one, I don't think we want that. We shouldn't set up the CNAME for now at least.

[davelab6]

upon accessing the new website you're redirected to the old one

I don't see that? What URL? :)

[davelab6]

Oh dear, I get an infinite loop redirect.

[davelab6]

It seems that when I added a CNAME file with fontforge.org, and asked Tony to update the DNS, until he does so, that requests for fontforge.github.io would be 301 redirected to fontforge.org, which (thanks to its .htaccess file) are 301 redirecting back to fontforge.github.io

So I changed the CNAME file to new.fontforge.org and we have to wait for Github's system to propagate that update, and then it will all start pointing to fontforge.github.io again, and then when Toby confirms the domain is updated, I'll update the CNAME file again and we should be good

[adrientetar]

We should just remove CNAME by now so that the website is accessible. new.fontforge.org is a 404.

[davelab6]

Agree, doen