Skip to main content
Denis Paris
Obsidian and Astro Combined

From Friction to Flow - Why I Switched to Obsidian + Astro

• 1 min • 210 words
blogging workflow obsidian astro

I used to have a recurring nightmare about my blog. Every time I had an idea, I’d open VS Code… and hit a wall.

The Friction of “Developer Blogging”

I knew Markdown. I knew frontmatter. But knowing the syntax didn’t make the process less painful.

My old workflow killed my creativity:

  1. Create a file: posts/2024-03-21-my-great-idea.md.
  2. Write the frontmatter: Copy-paste from an old post. Change the date. Forget the format. Google “ISO 8601”.
  3. Add an image: Find an image. Save it to public/images/posts/2024/. Rename it. Go back to the markdown file. Type ![Alt text](/images/posts/2024/my-image.jpg). Realize I got the path wrong. Fix it.
  4. Write the post: Start typing. Want to link another post? Go find the file path. Copy it. Paste it.

By the time I was ready to write, my energy was gone. I was debugging configuration, not crafting stories.

“Am I a writer, or a YAML configurator?”

Enter the Vault CMS

I switched to Astro Modular + Obsidian to stop fighting my tools.

The philosophy: Write where you think.

For me, that’s Obsidian. It holds my daily notes, drafts, and research. Why force my blog into a separate, sterile environment?

1. No More Frontmatter Fatigue

In Obsidian, I don’t type YAML. I use properties. Click “Add Property”, fill it in. Done. No more indentation errors crashing the build.

2. Images Just Work

This is the game-changer.

  • Old Way: Save, rename, move, copy path, paste path, pray.
  • New Way: Drag image. Done.

The system handles paths and optimization. I just see the image.

Linking used to mean manual file lookups. Now, I type [[, autocomplete the title, and I’m done. It feels like building a knowledge base, not wiring a website.

The Best of Both Worlds

I didn’t lose the developer benefits, either.

It’s still Astro under the hood. Fast. Tailwind ready. Full control if I want it, zero overhead if I don’t.

Push to Git. Live.

Conclusion

Creativity’s biggest enemy is friction. I thought I needed a “pro” editor to be a “tech blogger.”

I was wrong. I needed a tool that got out of the way.

If you’re struggling to publish, look at your tools. Do they aid flow, or add friction?

This stack is my answer. Now, if you’ll excuse me, I have writing to do.