Diagram

When building a personal blog, modern web development defaults to overkill. Setting up dynamic frameworks (like Next.js, Remix, or MERN stacks) with backend databases, authentication layers, and real-time APIs introduces a massive maintenance burden, security attack surface, and slow page-load times.

For a blog, static HTML is the ultimate architecture. This blog is powered by Quickblog, a lightweight static site generator designed for the Clojure/Babashka ecosystem by Michiel Borkent (@borkdude).

Here is a breakdown of how it works under the hood and why this architecture is a superior design choice.


1. The Core Runtime: Babashka

At the heart of Quickblog is Babashka, a fast-starting scripting runtime for Clojure.

Traditional Clojure runs on the JVM, which is powerful but suffers from a slow startup time (often several seconds)—making it tedious for quick CLI utilities and scripts. Babashka solves this by using GraalVM to compile the Clojure interpreter into a native binary. This gives us: - Instant startup (measured in milliseconds). - Zero JVM overhead on the host. - A rich subset of Clojure libraries (like shell execution, filesystem navigation, and HTTP client/server) pre-baked into the runtime.

Quickblog is executed entirely as a Babashka task defined in bb.edn.


2. Compilation Flow

Quickblog’s architecture follows a clean, functional pipeline:

<div style="display: flex; flex-flow: column; gap: 8px; max-width: 420px; margin: 24px auto; font-size: 14px; line-height: 1.5;">

<div style="display: flex; gap: 8px; flex-wrap: wrap; justify-content: center;">
  <div style="border: 2px solid #6366f1; background: #eef2ff; border-radius: 10px; padding: 10px 16px; text-align: center; flex: 1; min-width: 120px;">
    <strong style="font-size: 13px;">📝 Markdown Posts<br><span style="font-weight: normal; font-size: 11px;">/posts</span></strong>
  </div>
  <div style="border: 2px solid #0891b2; background: #ecfeff; border-radius: 10px; padding: 10px 16px; text-align: center; flex: 1; min-width: 120px;">
    <strong style="font-size: 13px;">🎨 HTML Templates<br><span style="font-weight: normal; font-size: 11px;">/templates</span></strong>
  </div>
  <div style="border: 2px solid #d97706; background: #fef3c7; border-radius: 10px; padding: 10px 16px; text-align: center; flex: 1; min-width: 120px;">
    <strong style="font-size: 13px;">📦 Assets<br><span style="font-weight: normal; font-size: 11px;">/assets</span></strong>
  </div>
</div>

<div style="text-align: center; font-size: 22px; color: #64748b;">↓ bb quickblog render</div>

<div style="border: 2px solid #059669; background: #d1fae5; border-radius: 12px; padding: 14px; text-align: center;">
  <strong style="font-size: 15px;">🌐 Pure HTML/CSS/RSS<br><span style="font-weight: normal; font-size: 12px;">/public</span></strong>
</div>

<div style="text-align: center; font-size: 22px; color: #64748b;">↓ Git Push</div>

<div style="border: 2px solid #7c3aed; background: #f5f3ff; border-radius: 12px; padding: 14px; text-align: center;">
  <strong style="font-size: 15px;">🚀 GitHub Pages</strong><br>
  <span style="font-size: 12px; color: #64748b;">HTTPS CNAME → nurazhar.com</span>
</div>

</div>

Ingestion: It reads raw Markdown files from the /posts directory and reads configuration parameters from bb.edn. 2.

Metadata Parsing: It extracts frontmatter metadata (Title, Date, Tags, Description) from the top of each Markdown file. 3.

HTML Transformation: Using Clojure-based parsing engines, it transforms Markdown syntax into clean HTML. 4.

Templating: It uses Selmer (a Django-like templating library written in Clojure) to wrap the rendered Markdown inside your main HTML layout (/templates/base.html, /templates/post.html, etc.).

Expanded Context

Feed & Index Generation: It automatically aggregates posts sorted by date to generate: - index.html (the homepage loading up to NN posts). - archive.html (a list of all posts). - tags.html (filtered views). - feed.xml (RSS feed). 6.

Output: All static resources are placed into a single /public directory, ready to be hosted anywhere.


3. Why This Design is Superior (The Pros)


Conclusion: Emulating Satoshi’s Design Philosophy

In his original 2008 Bitcoin v0.1 release, Satoshi Nakamoto focused on peer-to-peer simplicity—designing a system with direct nodes, no unnecessary intermediate layers, and raw efficiency.

Quickblog mirrors this philosophy in web development. By stripping away heavy JS frameworks, hydrations, client-side state managers, and database servers, it leaves you with exactly what the web was built for: clean, readable, and immortal HTML.