How this blog works

This blog has no database and no admin panel. Every post is a Markdown file in the same repository as the portfolio, and publishing is a git push. Here is how it fits together.

The flow

1. I add a Markdown file to content/blog/.
2. I commit and push it.
3. Cloudflare Pages runs next build and redeploys the static site.
4. The post is live at devsaifops.com/blog/<slug>.

That is the entire pipeline. Nothing to log into, nothing to pay for, and every post is version-controlled.

Writing a post

Each file starts with a small block of frontmatter, then the body in plain Markdown:

---
title: "My post title"
date: "2026-10-30"
summary: "One or two lines that show up in the list and previews."
tags: ["Backend", "Notes"]
---

Your writing goes here. Headings, lists, **bold**, links, and code all work.

Why static

The site is a Next.js app exported to static files, so the blog is built once at deploy time and served from the edge. It is fast, it costs nothing to run, and there is no server to patch. For a writing blog, that is exactly the right trade.

Boring infrastructure is a feature. The less there is to break, the more time goes into the writing.

If you are reading this, it worked.