Engineering

Delete the Framework From Your Blog

A blog is the one project where the runtime is pure overhead. Here is the argument, and the build that settles it.

2 min readPublished June 24, 2026
Share on X

Every blog framework starts by making a promise: give me a folder of Markdown and I will give you a site. The promise is real. What it costs you arrives later, in the bundle.

For a site whose entire product is readable text, the runtime is the largest single cost and it buys almost nothing.

What the runtime actually costs

Not the kilobytes, exactly — those are measurable and cheap. The cost is what it makes impossible:

  • You cannot see the HTML a crawler sees without running a build.
  • You cannot serve the site from anywhere but a runtime, so the host is a decision.
  • A page that errors at runtime has no content at all, because the content lived in JavaScript.
  • Every reader downloads code for pages they may never open.

What static gets you

A build step that renders every route to a file. The crawler gets the same bytes you do. The host is a directory on a disk. A broken deploy fails loudly at build time rather than quietly in production.

npm run build
# 1. vite build              -> hashed JS + CSS in dist/assets
# 2. vite build --ssr        -> a renderer in .ssr/
# 3. node scripts/prerender  -> one HTML file per route

Three commands and the third one is a plain Node script using `react-dom/server`, which was already installed. No plugin, no browser download, no headless Chrome in the install.

Where this stops working

The moment a page genuinely differs per visitor — a logged-in dashboard, a cart, a comment form that has to post — a runtime is not optional, and pretending otherwise is how static sites get an awkward bolt-on API within a year.

A blog is the clean case. That is why it should be the easy one.

  • Static Sites
  • Web Development
  • Performance
KI

Kadirul IslamVerified author

Founder, A.K Solution

Follow on X

Founder of A.K Solution. Full-stack engineer building AI agent tools like KiCode, JSON form engines like ki-forms, and high-scale SEO systems. Obsessed with shipping fast, zero-bloat software that lasts.

More from Kadirul Islam

Cache Policy Is a Design Decision

Immutable, revalidate, or no-store. Choosing wrong is how you ship a 200 for a URL that should not exist.

2 min readCaching

The CSS Bug That Silently Deleted a Design System

One attribute selector outranked every component class in the build. Nothing threw, nothing warned, and the page just looked wrong.

2 min readCSS

The Router I Did Not Install

Two routes do not need a routing library. They need about forty lines and a hydration contract you can state in one sentence.

3 min readReact

Prerender Everything and Ship a Static Site

If two visitors receive identical bytes, a server runtime is a tax you agreed to pay for nothing.

2 min readWeb Development