Hello this is my blog. I made this to document the projects i make. Zola 2026-07-24T00:00:00+00:00 https://blog.errornoslash.be/tags/nixos/atom.xml 2026-07-24T00:00:00+00:00 2026-07-24T00:00:00+00:00 Dias Stas https://blog.errornoslash.be/blog/how-i-built-this-blog/ <p>Every blog needs a first post, and the least original — but most honest — thing I can write about is the blog itself. So: here's what's holding this page up, and the one thing that fought me the whole way.</p> <h2 id="the-stack">The stack<a class="post-anchor" href="#the-stack" aria-label="Anchor link for: the-stack"><span aria-hidden="true">#</span></a> </h2> <p>It's a <a href="https://blog.errornoslash.be/blog/how-i-built-this-blog/%5Bhttps://www.getzola.org/%5D(https://www.getzola.org/)">Zola</a> site. One static-site-generator binary, no Node, no 400-package <code>node_modules</code> to audit. I write Markdown, Zola spits out HTML, and that's the whole content pipeline.</p> <p>On top of it sits the <a href="https://blog.errornoslash.be/blog/how-i-built-this-blog/%5Bhttps://github.com/klritunu/terminus%5D(https://github.com/klritunu/terminus)">Terminus</a> theme, which gives me the <code>dias@stas:~/blog $</code> terminal look for basically free. I swapped in my own <code>errorno-dark</code> palette and a custom stylesheet so it feels like mine and not a demo, but the bones are all Terminus.</p> <p>Deploy is a GitHub Actions workflow: push to <code>main</code>, it builds the site and publishes it to <code>blog.errornoslash.be</code>. No server to babysit — the output is just files.</p> <h2 id="editing-without-touching-the-terminal">Editing without touching the terminal<a class="post-anchor" href="#editing-without-touching-the-terminal" aria-label="Anchor link for: editing-without-touching-the-terminal"><span aria-hidden="true">#</span></a> </h2> <p>The part I actually wanted was to write posts <em>without</em> opening an editor and hand-writing TOML front-matter every time. That's where <a href="https://blog.errornoslash.be/blog/how-i-built-this-blog/%5Bhttps://pagescms.org/%5D(https://pagescms.org/)">Pages CMS</a> comes in. It reads a <code>.pages.yml</code> schema straight out of the repo, then gives me a proper form — title, slug, date, tags, a rich-text body — and commits the resulting Markdown back to GitHub for me. The post you're reading was written through that form.</p> <p>The nice bit is that the CMS is <em>just a view</em> onto the repo. If it ever disappears, my posts are still plain <code>.md</code> files sitting in <code>content/blog/</code>. No lock-in, no export dance.</p> <h2 id="what-broke">What broke<a class="post-anchor" href="#what-broke" aria-label="Anchor link for: what-broke"><span aria-hidden="true">#</span></a> </h2> <p>Naturally, the friction wasn't the CMS or Zola — it was <em>logging in</em>.</p> <p>Getting into Pages CMS means authenticating with GitHub, and I use a passkey stored in Proton Pass. On a Firefox-based browser (I'm on Zen), that handoff isn't automatic: Firefox routes the WebAuthn request straight to the OS platform authenticator, so instead of a nice Proton Pass popup I got the system's <em>"Touch your security key"</em> dialog and GitHub grumbling about "partial passkey support." The extension never got a look in.</p> <p>The fix lives in <code>about:config</code>, and the annoying part on a declarative NixOS setup is making sure the pref survives a rebuild instead of getting reset the next time I <code>switch</code>. Lesson filed under <em>"the login page is always harder than the app."</em></p> <h2 id="what-s-next">What's next<a class="post-anchor" href="#what-s-next" aria-label="Anchor link for: what-s-next"><span aria-hidden="true">#</span></a> </h2> <p>Now that the pipeline works end to end, the plan is to actually use it: write-ups of the projects I've been building and the NixOS config I keep poking at more than is strictly necessary.</p> <p>If you're reading this, the deploy worked. See you in the next one.</p>