← back to the notebookrésumé · pdf
page §  ·  dispatch · building-my-blog-with-claude-code  ·  pml-fn-§
← all dispatches
June 1, 2025 · by Vyshnav S Deepak · 2 min read

Building My Blog with Claude Code in 10 Minutes

I asked Claude Code to add a blog to my Next.js site. Ten minutes later, I was writing this post on that very blog. Here's how it went down.

🤖 AI & Automation#AI Tools#Web Development#Next.js#Developer Productivity#Blogging

I'm writing this post on the blog that Claude Code built 10 minutes ago. Wild.

Claude Code Terminal

The Prompt That Started It All

Me: "it is my personal website, it doesn't have a blog yet. I'm thinking of using Payload cms and getting something done. what are the other best options available to continue on vercel hosting"

Claude listed 6 options with trade-offs. I picked MDX for simplicity. One more message: "lets do mdx"

That's it. That's all I typed.

What Claude Did

In about 10 minutes, Claude:

  • Installed the right MDX packages plus utilities for reading time
  • Configured Next.js to handle .mdx pages
  • Created a clean blog structure that matched my existing app layout
  • Hooked into my shadcn/ui components for consistent styling
  • Added "Blog" to my nav by editing my ProfileCard component
  • Set up typography styles that just work
  • Built in proper error handling (404s for missing posts)

The only correction I made? Telling Claude I use pnpm, not npm. It adjusted instantly.

The Smart Choices

What impressed me wasn't the boilerplate — it was the thoughtful decisions:

MDX just made sense. No external CMS to manage, no API keys, no separate hosting. Everything lives in my repo where I can version control it with git. Perfect for my workflow.

Reusing what I had: Instead of creating new components, Claude hooked into my existing UI system. The blog listing uses my Card components. Individual posts respect my existing typography.

The little things: Reading time calculation, date sorting, frontmatter parsing — all those features you'd eventually add were just there from the start.

My Development Philosophy

I commit after each meaningful change. Git is my safety net. Claude respected this perfectly — every change was atomic and testable. No giant rewrites, just incremental improvements I could verify and commit.

The Reality Check

Setting this up manually? At least an hour of:

  • Reading MDX docs
  • Figuring out Next.js configuration
  • Building the file reading logic
  • Styling markdown content
  • Wiring up routing

Claude compressed all that into a 10-minute conversation. I didn't think about configs, imports, or file structure. I just said what I wanted and watched it happen.

What This Means

This isn't about AI replacing developers. It's about focusing on what matters. I wanted to write blog posts, not build a blog system. Claude handled the implementation so I could jump straight to creating content.

The fact that you're reading this on that same system, built minutes ago, still blows my mind.

Welcome to the future — where "I want a blog" becomes a working blog before your coffee gets cold.


P.S. - Yes, I wrote this myself. Though asking Claude to help structure it felt appropriately meta.