Why I use a static website

Sun, 10 May 2026 00:00:00 +0000

The site you’re reading lives as a folder of plain Markdown files. A tool turns them into HTML. GitHub serves the HTML. That’s it. No database, no PHP, no React app, no backend, no analytics SDK, no cookie banner. I keep choosing this setup over the modern alternatives — Substack, Medium, Wordpress, Notion sites — and people sometimes ask why. Here’s the answer.

It loads instantly Link to heading

A static page is a finished file. Your browser asks for it; the server hands it over; you read it. There’s no template to render, no database query to wait for, no JavaScript framework to spin up. On a slow connection or on a phone with a tired battery, the difference is obvious — the page is just there.

Markdown on pmslava

Why I use a static website

It loads instantly Link to heading