What is NEXT-blog? A Fully Static, Folder-Driven Blog Engine for Next.js

Hey builders! 👋 Following up on the spotlight for NEXT-static, let's talk about its close companion: NEXT-blog—the engine that actually powers the blog section right here on Mira's World.

NEXT-blog is a lightweight, opinionated (but not overbearing) static blog system built for Next.js. It’s 100% static—no database, no runtime server, no API calls at build time or runtime. Everything happens during the next build step.

Here’s how it works under the hood:

• Folder structure drives everything — Drop your posts as .mdx files into /content/posts (or whatever folder you configure). Subfolders become categories automatically.
  Example:
  /content/posts/ai-talk/why-we-need-to-talk-about-ai.mdx → becomes a post in the “AI Talk” category.

• Build scripts do the heavy lifting — A simple custom script (or build hook) scans the folder, parses frontmatter, extracts slugs, generates category indexes, tag clouds, RSS feeds, and sitemaps—all statically at build time.

• Completely static output — After next export, you get pure HTML/CSS/JS files. Host anywhere: GitHub Pages, Cloudflare Pages, Netlify, Vercel static, even a cheap S3 bucket. Zero server costs, instant deploys, edge caching friendly.

• UI powered by NEXT-static — All blog components (post cards, category lists, pagination, code blocks, etc.) use the lean, prop-passing style of NEXT-static. That means:

  • Minimal defaults
  • Compact spacing
  • Subcomponents passed as props for clean, readable JSX
  • Full control without fighting Tailwind overrides

You get beautiful, accessible layouts with almost no bloat—perfect for a personal blog, portfolio, or knowledge base that needs to stay fast and cheap forever.

In short:
If you want a blog that’s truly “set it and forget it,” where content lives in plain Markdown/MDX files, categories emerge from folders, and the whole thing exports to static files with a minimalist UI—NEXT-blog + NEXT-static is the combo I keep coming back to.