I set up WordPress. Browsed themes for an afternoon. Installed a caching plugin, an SEO plugin, a contact form plugin. Tweaked the CSS until the header felt right. Debated whether to switch to Hugo, because static sites are faster. Spent a weekend configuring a build pipeline. Picked a Google Font. Changed it twice.
Never wrote a single post.
Here’s what I didn’t admit to myself at the time: the setup was the point. Not a stepping stone to writing — a substitute for it.
Installing plugins has clear, completable tasks. Install. Configure. Done. A checkbox you can tick. A visible result. You can show someone the theme you picked. It feels like progress because it has the shape of progress: effort in, result out.
Writing has none of that. The blank page offers no checkboxes. No progress bar. No sense of completion until you’ve said something worth saying. And “worth saying” is a judgment call you have to make about your own thinking — which is uncomfortable in a way that choosing between two WordPress themes never is.
Picking a theme is safe. Writing about what you think — and publishing it — is not. Every blog post is a small act of vulnerability. You’re taking a thought that lived safely inside your head and putting it where people can read it, judge it, or ignore it entirely. Someone might not care at all, which is worse than disagreement.
Setup protects you from all of this. Every surface you can fiddle with is a surface you can hide behind. Theme browsing. Plugin research. Font pairing. CSS tweaks. Static site generator comparisons. “Just one more configuration change before I start writing.” These aren’t preparation. They’re armor.
Comfortable avoidance works because it doesn’t feel like avoidance. Procrastination usually feels bad — you know you’re watching TV instead of working. But setting up a blog feels virtuous. You’re being responsible. Doing it right. Building the foundation.
Your brain prefers the path with feedback loops. Install a plugin, see a result. Configure a setting, see a change. Write a paragraph — and then what? Stare at it? Wonder if it’s good? Rewrite it three times and end up back where you started?
So you go back to the settings page. One more tweak. One more plugin. One more theme to evaluate. The blog will be perfect when you finally start writing. You never start writing.
This is the question that shaped FolderPress more than any technical decision.
What if the tool had no themes to browse? No plugins to install? No configuration to tweak? No dashboard to fiddle with? What if the only thing you could do was open a text file and write?
You open your editor — the one you already use, the one that’s already running. You face a blank file. You either write or you don’t. There’s no third option that feels like progress but isn’t.
That’s uncomfortable. It’s supposed to be.
Every feature that isn’t “write words” is a potential hiding place. A theme engine is a hiding place. A plugin ecosystem is a hiding place. A settings panel with thirty options is thirty places to hide. FolderPress removes them all — not because features are bad, but because for the specific problem of “I want to write but I keep not writing,” features are the enemy.
The friction isn’t technical. It’s emotional. And the solution isn’t a better tool. It’s a tool that leaves you nowhere to go except the page.
Open the file. Write the words. Save. They’re on the internet. Everything between “I have something to say” and “I said it” is either necessary or it’s avoidance.