lists.tlug.jpfor the scraped copy of the current lists site. I didn't do any other subdomains; @ragga things we should just drop them and I agree. Everything should be pretty fully documented but ask here if you have questions.
At a quick glance, all looks good except the archive user/pw images which don't load on new.tlug.jp. Was that intentional?
In any case, lists.tlug.jp is now pointed at Jims server and looks to be working fine, which is kinda the most important as it's the portal for the mailing list.
Going forward, I think the main pages on both tlug.jp and lists.tlug.jp will have to be checked for consistency anyway.
masterevery time we did a commit. Perhaps it's not clear, but the release branch is an entirely different set of files from the source branch. It's basically a commit of everything under the
_sitedirectory and nothing else.
d790d918d407c9fe2a. (The details of that are in the
netlify-testrepo.) I think it would be worth tweaking the message on any of those you notice, so we don't get someone a year from now saying "I disagree with that obvious aesthetic decision" and breaking the site.
netlify-test. It looks like there may be enough stuff to be fixed on this branch that it might be worth just rolling it back to the previously released commit, re-releasing that, and then doing a pass to go through and fix things.