Skip to content


Near Arthur's Pass, New Zealand

Content Management

I have a bit of a habit with websites. Instead of constantly posting boatloads of content, I tend to play around with the systems themselves. Prior to the page you're viewing, I was using a system called Grav. It worked fine, but in my search for better, I've found a new system.

Grav stands out for its approach to being text-centric. It's markdown with a system-side interface. You set it up on a typical web server, and you don't need anything else. No database needed. Not bad, but it's an extra layer of nonsense... lots of plug-ins, backups, and other things to be managed.

I've decided to move forward to Material for MKDocs. This project doesn't seem like a "content management system", but indeed it is. It just has to be set up properly. So instead of installing and FTPing files to a server, installing PHP and whatever else, there's a simpler way. GitHub+Material is that way.

I'll post more about this later, but for now, the system is accessible like code - just any VSCode or text editor of your choice will do. Put the files on GitHub within the .io repo, set an Action to publish on check-in, and point your domain to the .io site. Material as a "theme" (it's more than that) is kept up-to-date through GitHub. All you do is write Markdown, and this time, you can do it without having to log into your own server to change things. (Granted Grav could be sonfigured to pull and build on a timer...)

The benefit is a fast static site, hosted on GitHub, and a far better setup than any Jekyll nonsense. No yaml needed. And static without having to build locally and repub; the build is in the repo.

I have some test pages and details that are scattered around, but if you're able to check in a change on GitHub, you can have a site like this, for free.

I hope you find something here that's helpful to you if you've popped in. Thanks!