Disable GitHub Pages site and replace with site under latex-project.org

[zauguin]

Currently the page created by this repository is reachable under https://latex3.github.io/tagging-project/ and under https://tagging-project.latex-project.org/. This leads to issues since the links assume that the base URL is https://latex3.github.io/tagging-project/, so some links are leading to unexpected locations when viewed under https://tagging-project.latex-project.org/.

My suggestion is to change the configuration to fully use the https://tagging-project.latex-project.org/ URL and stop deploying to https://latex3.github.io/tagging-project/. Alternatively we could also do the opposite and remove the https://tagging-project.latex-project.org/ version again.

[davidcarlisle]

hmm I wasn't aware until yesterday that the latex-project.org version existed:-)

https://latex3.github.io/tagging-project/

Is somewhat widely advertised as the main landing page for tagging information so if we do move to tagging-project.latex-project.org I think we'd have to keep this with redirects (presumably we could still run gh-pages from a branch and make it have whatever we wanted it to have)

[zauguin]

hmm I wasn't aware until yesterday that the latex-project.org version existed:-)

Well, the latex-project.org version didn't exist before yesterday. I thought that I can add it in parallel to the existing site so it shouldn't affect anyone for now. Then I opened this as a place for discussion once I realized that just having them in parallel is somewhat problematic. Anyway personally I think that having it under latex-project.org would be nicer, but I also wouldn't mind to just stay with https://latex3.github.io/tagging-project/ and drop the other version again.

I think we'd have to keep this with redirects

Sadly redirects in GitHub Pages don't really work (at least not HTTP redirects, <meta tags or JavaScript could probably be done). Alternatively we could also keep the old site running as is and deploy to both. (It's not as easy as I originally thought, but also not that hard if we actually want to do it)

[davidcarlisle]

Sadly redirects in GitHub Pages don't really work

yes I know (you have to use html meta redirects) but that's probably enough for human readers landing on the site (eg from any number of project talk pdfs describing the project) github pages is what it is so if the redirection is in that direction that's all that can be done. texfaq.org makes a lot of use of that kind of redirect and in practice no one has ever complained.

I suppose another alternative would be to set latex-project.org up the same way as if it were a standard github pages custom domain in which case the tagging-project site would appear as latex-project.org/tagging-project not tagging-project.latex-project.org then relative links just work if you use the existing jekyll constructs that are expecting that?

We should probably also consider babel, the other large site currently under latex3.github.io

[gucci-on-fleek]

@zauguin

I think we'd have to keep this with redirects

Sadly redirects in GitHub Pages don't really work (at least not HTTP redirects,

I just did this a few months ago; it's undocumented and a little annoying to set up, but it works fairly well. You need to first set the new site up as a custom domain in https://github.com/<user>/<repo>/settings/pages. GitHub will make you set up a CNAME record on the target domain pointing to some special GitHub domain, and afterwards it will redirect the https://<site>.github.io links to the new domain that you set up. But, the trick is that after you've set this up and GitHub has validated the DNS records, you can change the DNS back to whatever you want, and GitHub will continue redirecting https://<site>.github.io to the target domain, even if it's no longer hosted by GitHub.