upgrade to latest cstate and hugo

this site has been running cstate happily for a long time now, but i don't believe it has never been updated. hugo is probably still running some old thing.

we should fix that, and make sure we keep fixing it again, probably through @renovate-bot.

added Next label

assigned to @anarcat

notable: https://github.com/cstate/cstate/issues/183 is fixed, so 404s should be better now, to be tested and confirmed.

the tor project is mentioned as a user on the frontpage: https://cstate.netlify.app/ so it seems like a good idea to show the good side of this project, instead of an old rotten 2 year old version.

we're running 4.4. there's a ton of changes since then:

• 5.3 introduced component links
• 5.2 introduced pinned informational posts which might help with #12
• 5.1 introduced SVG badges for services, maybe @donuts would like to make us some pretty graphs here?
• 5.0 introduced a lot of things including breaking changes and a bumped hugo dep (to 0.8): the config file needs a rewrite, all dates need to be in UTC, but now we get last modification timestamps, category status

so yeah, not a trivial update, but worthwhile. i'm particularly irritated by our "outage lasted 300h" messages, hopefully those are fixed?

we should fix that, and make sure we keep fixing it again, probably through @renovate-bot.

procedures on that are well documented in https://gitlab.torproject.org/tpo/tpa/renovate-cron/

it looks like we "just" need to invite @renovate-bot as a Developer in this project and everything that happens after is Magic.

just for kicks, i invited @renovate-bot, maybe it will do all of this for us?

(no, i know, we'll probably need to update config.yml and change dates, but it can do the stupid parts at least.)

mentioned in merge request !45 (merged)

mentioned in commit 9195938f

closed with merge request !45 (merged)

thanks to @micah and @renovate-bot, this was almost easy! i still had to manually change config.yml in !45 (merged), but that was relatively easy.

now we have an up to date site, and a bot that will make sure it stays that way, whoohoo!

marked this issue as related to #34 (closed)

marked this issue as related to #35 (closed)

opened #35 (closed) and #34 (closed) to followup on those new features, otherwise all done here.