How this site works: plain HTML on GitHub Pages

September 30, 2026

This site has no framework, no build step, and no CMS. It's a folder of hand-written files, and I think that's a feature.

The stack

• HTML — each page and post is one .html file.
• CSS — a single style.css shared by every page.
• GitHub Pages — the repo is named grsh50.github.io, so GitHub serves the files on the main branch as a website at the matching URL.

Why no generator?

Static site generators are great, but for a personal blog they add a layer I'd have to maintain: dependencies, themes, build configs, upgrade churn. With plain files, the site I edit is the site that ships. There's nothing to break and nothing to update except my own words.

The publishing workflow

Writing a new post means:

• Creating a new .html file under posts/.
• Adding one entry to the list on index.html.
• Committing and pushing.

GitHub Pages picks up the push and the post is live within a minute. That's the entire pipeline.