Loading post
Notes from the workshop.
Writing about web development, AI tooling, and the occasional lesson learned the hard way.
Loading posts
Notes from the workshop.
Writing about web development, AI tooling, and the occasional lesson learned the hard way.
Loading posts
Loading post
Tell us what you're building. We'll tell you if we're the right fit — and if not, we'll point you somewhere that is.
We build content management systems for clients. When it came to our own blog, the obvious question was whether to build another one or rent one.
We looked at three ways to do it.
| Where posts live | Who can write | What it costs us | |
|---|---|---|---|
| A git-based editor | Files in the code repository | Anyone with a GitHub account | Every post is a deploy |
| A hosted CMS | Someone else's servers | Anyone with a login there | Another account, another vendor |
| Our own admin | Our own Firebase project | Anyone we allow in | We build and maintain it |
We chose the last one, for three reasons.
Content platforms are one of the studio's services. A blog that runs on our own admin is the same kind of thing we hand over to clients: a login, an editor, a media library, and publishing that doesn't need a developer. If something about it is awkward, we're the first to find out.
The site already uses Firebase for its data, so posts sit in the same Firestore database as everything else, images go to Firebase Storage, and sign-in is Google through Firebase Authentication. Only the studio's own accounts are allowed into the admin; anyone else who signs in is turned away by the server.
Posts are written in markdown, in a proper code editor with a live preview beside it. The preview isn't an approximation: it uses the same renderer as the published page, on the same graph paper.
Markdown here also means MDX, so a post can drop in a few of the site's own components — a portfolio project, a Lab exhibit, a video, a note like this one:
A hosted CMS would have been running in an afternoon. This took longer, and we maintain it ourselves. For a studio that builds these systems, that's the point: we'd rather find the rough edges in our own admin than in a client's.
From the portfolioNobility Care AustraliaCompany Website · See the project →