A Content System That Removes Excuses

Most content systems are too clever.

They have a planning board, a capture app, an AI prompt library, a review queue, a repurposing workflow, and five places for drafts to die.

That setup looks productive. It also gives you a hundred places to stall.

What finally worked for me was cutting the system down until it was almost boring.

An idea goes into a markdown file. The post lives in Astro. The repo goes to GitHub. The site ships through Vercel. That’s basically it.

I still use AI while writing. I’m not pretending otherwise. But the useful part isn’t “AI content generation.” The useful part is removing friction between having a thought and publishing it.

The real enemy is drag

When people say they want to post more, what they usually mean is they want to feel more consistent.

Consistency is not a motivation problem. It’s a drag problem.

If publishing requires opening three apps, cleaning up a draft, moving text into a CMS, uploading an image, fixing formatting, and checking whether the slug broke, you will absolutely find a reason to do it tomorrow.

That’s why I moved toward a simpler publishing setup. I already wrote about why I switched to Astro. The bigger lesson wasn’t about frameworks. It was about reducing the number of excuses available to me.

My current rule

The system should make the next step obvious.

For me that means:

write in one place
publish from the repo
keep the frontmatter predictable
use one image format
avoid any step that needs me to “figure it out again”

That last one matters more than people think.

A lot of workflow pain comes from re-deciding little things. What’s the right metadata format? Where does the image go? Which path does the URL use? Did I call this a tag or a category? Tiny questions, but they add up.

If the system answers those questions for me up front, I write more. If it doesn’t, I procrastinate while pretending I’m being thoughtful.

AI helps, but not where people think

The boring truth is that AI is better at compression than commitment.

It can help me sharpen an angle, pressure test a claim, or turn a half-formed note into something clearer. That’s useful.

But AI does not create a publishing habit by itself.

The habit comes from having a system where the path from draft to live post is short and repeatable.

This is the same reason a lot of “AI workflow” products feel impressive in demos and annoying in real life. They add capability while quietly adding drag. And if your real bottleneck is drag, more capability can make the problem worse.

The Astro content collections docs are a good example of the opposite approach. It’s just a clean content model. Not flashy. Very little mystery. That kind of simplicity compounds.

What I’m optimizing for now

I’m not trying to build the most advanced content machine on the internet.

I’m trying to build a system I will still use on a random Thursday when I’m busy, distracted, and not particularly inspired.

That standard is underrated.

A workflow that only works when you’re energized is not a workflow. It’s a mood.

The best systems survive low motivation. They reduce the gap between intention and action until posting feels almost mechanical.

That’s what I want from tooling now. Less ceremony. Less reinvention. Fewer moving parts.

Not more ideas about content.