wyrdstone.wiki

This is a side project I put together to help run a tabletop campaign I’m part of — Mordheim Australis 2027, based on the old Games Workshop skirmish game Mordheim. It started small and grew because the tools I needed didn’t quite exist yet.

wyrdstone.wiki is a static site I built to hold the campaign’s rules, house rules, standings, and reference pages for warbands — including a lot of community-made factions that never got official support. It’s not fancy; it’s a Quartz site pushed through GitHub to Cloudflare Pages, but it does the job of keeping everyone on the same page.

The other half is a set of digital warband templates for Quartermaster, an iOS army-list app that a lot of us use at the table. I don’t have a background in software development — I’ve worked with the app’s developer to extend it to cover warbands it didn’t originally support, learning the toolchain and the file formats as I went, and building out validation and checks along the way so I could trust what I was shipping.

Neither piece is finished, and I’m sure there are rough edges I haven’t found yet. But it’s been a good excuse to learn some new skills in service of a hobby I care about, and hopefully it makes the campaign a bit easier for everyone playing in it.

How it’s built

• Quartz v4, a static site generator for Markdown notes
• Content in a GitHub repository
• Deployed to Cloudflare Pages on every push

What I’d do differently

Looking back, the big one is starting on Quartz v5 instead of v4, which we now have to migrate to later. Beyond that, we learned the hard way to trust actual file state over session summaries and briefings, after a few cases where reported fixes weren’t actually in the code. We’d also build in more upfront schema verification (catching edge cases like silent YAML-to-plist failures) rather than adding those checks only after something slipped through.