Migrate site to Zola (fixes #7)

[17cupsofcoffee]

look upon ye and despair, at the largest PR diff mankind has ever seen

While I was initially not a fan of the idea of migrating the site across to a different generator, a few things have swayed me the other way recently:

• 99% of the site's maintainance is being done by @ozkriff, and their preference was Zola.
• My personal site is also using Zola, and I'm missing a few of its features when I'm using Jekyll (anchor links, colocated assets, etc).
• The WG has just taken maintainership of AreWeGameYet, which is also a Zola site.
• ...and most importantly, I was bored and wanted to do some webdev 😛

So I've gone through and ported the existing theme and content across - as far as I can tell, it looks and behaves identically.

The main user-facing changes are:

• Zola doesn't support /YYYY/MM/DD/slug URLs, so the posts have been moved to /posts/slug. All existing posts have aliases defined, so existing links won't break.
• The Zola URL for an RSS feed is rss.xml, not feed.xml - again, I've added a redirect.

There's a live preview at https://mystifying-keller-336452.netlify.com - please feel free to snoop around for things that are broken :)

The main thing that would still need doing to get this ready to merge would be setting up the CI config - @ozkriff's expertise would be appreciated there 😄

[Lokathor]

Seems good from as much as I can tell, but I've got no real experience with blog engines.

[AlexEne]

Best pr ever :D

[ozkriff]

I've posted a few nitpick comments, but overall this is a great PR, thank you so much! 👏

[ozkriff]

lgtm!

[ozkriff]

So, let's merge this PR in a few hours if no one objects? :)

[zicklag]

This is great!

But...now the GitHub pages site just shows the README. If you guys want I can setup a Drone CI script for building the site and pushing it to GitHub pages.

[ozkriff]

For some reason, the source branch is still master (and not gh-pages) and I can't change it.

UPD: https://stackoverflow.com/questions/25559292/github-page-shows-master-branch-not-gh-pages ugh

[17cupsofcoffee]

So apparently this is working as intended - user/organisation page repos will only let you publish from master, unlike normal repos. This is silly, and I hate it.

That leaves us with three options:

1. Revert the PR, either temporarily or permanently.
2. Rename the repo to make it not be an organisation site (I think this is a non-starter, as it'd change the base URL of the site and break all the links that are already out there)
3. Rename our current master branch to something like source, and get the job to publish to master instead.

I think 3 would be an okay solution (as long as we switch the repo's default branch to source so that people don't see the static content when they look at https://github.com/rust-gamedev/rust-gamedev.github.io). How would people feel about that?

(Also, it figures I'd break the site the one night I'm away from my computer... Sorry 😅)

[Lokathor]

Option 3 sounds slightly goofy but very simple. Let's do that.

[kpp]

How would people feel about that?

It's fine because you can set source as a default branch and every PR will be targeted to source branch by default.

[Lokathor]

My one concern is if the github pages branch is actually "the default branch", and it will change when we change the default branch. I don't know how that works exactly.

[zicklag]

Another option, if the different branch doesn't work, would be to track the source in another repo and have CI push the built result to the organization repo's master branch.

[ozkriff]

3. Rename our current master branch to something like source, and get the job to publish to master instead.

Ok, I'll try this.

[ozkriff]

Aaand done. Set source as the default branch and enabled branch protection.

https://rust-gamedev.github.io/ seems to work fine again.

[17cupsofcoffee]

Excellent, thanks for sorting that out :)