Static vs WordPress: What a Writer Actually Needs

I've built websites both ways. WordPress for years, then I tore it out and went static, and I haven't looked back. So when somebody asks me "static site vs WordPress for writers," I don't give them the diplomatic answer. I give them mine.

Here's the short version. If you write words for a living, or you want to, you do not need a content management system. You need a place to put words that loads fast, costs almost nothing, and can't be taken from you. WordPress can be that. Usually it isn't. Let me show you the difference so you can decide for yourself.

What you're actually choosing between

A WordPress site is a program. It runs PHP, it talks to a database, it logs you in, it renders every page fresh on every visit. It's a living machine, and living machines need feeding.

A static site is a stack of files. HTML, CSS, a few images. The page already exists before anyone asks for it. The server just hands it over. There's no database, no login, no code running when a reader shows up. It's the difference between a restaurant kitchen and a vending machine. One can do more. The other never burns down at 2am.

For a writer, that distinction is the whole ballgame.

The two taxes WordPress charges

I've written this before and I'll keep writing it because it's true. WordPress charges a design tax and a maintenance tax.

The design tax is the editor sitting between you and the page. You drew a layout in your head. Now you fight the block editor, or the theme, or the page builder, until the thing on screen roughly resembles the thing you wanted. You're wrestling an abstraction instead of writing the page. Every custom idea is a negotiation.

The maintenance tax is worse because it never ends. PHP versions. Plugin updates that break other plugins. A database that needs backing up. A login screen that bots hammer all day, every day, forever. You didn't ask for a security surface. WordPress gave you one anyway, and now it's yours to defend. The average WordPress site gets compromised through an outdated plugin nobody remembered was installed. That's not a rare horror story. That's Tuesday.

For a one-person operation, both taxes are pure drag. You're a writer. Every hour you spend patching a plugin is an hour you didn't spend writing the thing people actually came for.

What static gives you instead

I replaced my CMS with a folder of markdown and a build step. I write the post in plain text. A generator turns it into the design I drew. It deploys as plain files. No database. No login. Nothing to patch in the dark.

The design didn't get worse when I did this. It got exactly what I drew, because nothing sits between me and the HTML anymore. The mockup became the template, verbatim.

Speed is the other prize, and it's not a small one. Static files are about as fast as the web gets. There's no PHP spinning up, no database query, no plugin chain executing before the reader sees a word. The page is already there. Google notices. Readers notice. Your phone-tethered reader on a bad connection in a parking lot notices most of all.

And then there's the part I care about most. Ownership. A static site is a folder. It's mine. It can't be locked behind anyone's dashboard, can't be held hostage by a host's upsell, can't break because some company three states away pushed an update I didn't approve. I run my whole network this way and the box it lives on costs less than lunch.

When WordPress actually earns its keep

I'm not a zealot. WordPress is the right tool sometimes, and pretending otherwise makes me a liar.

Use WordPress when you genuinely need server-side machinery that has to run on every visit. Real e-commerce with live inventory and carts. A membership site with gated content and individual logins. A community with user accounts and comments and profiles. A directory people search and filter in real time. A site five non-technical people need to edit through a familiar dashboard.

Those are real jobs. WordPress does them, and rebuilding all that plumbing yourself on a static stack is a fool's errand. If your site's core feature is a thing that happens when a logged-in user clicks a button, you want a CMS. Stop reading. Go install WordPress.

But notice none of those describe a writer publishing words. None of them describe a blog, an essay collection, a portfolio, a newsletter archive, a small store of digital downloads. That's most of us. And for most of us, the machinery is overhead we pay for and never use.

The honest comparison

Cost. Static wins, and it isn't close. A static site hosts on cheap or free infrastructure with nothing to scale. WordPress needs a host that can run PHP and a database, which means managed hosting fees, which means a recurring bill that climbs the moment you get traffic.

Speed. Static wins. Pre-built files beat live-rendered pages every time, every benchmark, no asterisk.

Security. Static wins. There's no login to break into, no database to inject, no plugin to exploit. You can't hack a folder of HTML in any way that matters.

Ease of writing. Closer than people admit. WordPress hands you a dashboard with a publish button, which is genuinely friendly day one. Static asks you to write markdown and run a build, which sounds scary until you've done it twice, and then it's muscle memory. The friendliness flips fast.

Capability. WordPress wins, flatly. Anything dynamic, anything per-user, anything live, WordPress already has a plugin and static has a weekend of work you'll regret.

Dynamic features on static. Here's the move nobody tells you. You don't have to choose all or nothing. Keep the site static and bolt on a hosted service for the one dynamic thing you actually need. A form service for contact forms. A separate store for selling. A comment service if you want comments. The pages stay static and fast. The one dynamic piece lives somewhere built for it. You get the speed and the ownership without rebuilding a CMS to handle a single feature.

How I'd tell a writer to start

Don't overthink the tooling. Pick a static generator, learn to write a post in markdown, learn the one command that builds and ships it. That's the whole skill, and it's smaller than learning WordPress ever was.

Get your domain pointed at it, write your first real post, and publish. The first time you publish by pasting a draft and running one command, something clicks. You're not renting a spot in someone's machine. You own the press.

I document how I do all of it. The build logs and how-tos live in my guides, the running build journal is in the feed, the store I bolted onto the static stack sits at /store/, and the radio I run the same cheap way streams at /radio/. None of it touches a CMS. All of it is mine.

That's the real answer to static versus WordPress for a writer. Use WordPress when you need a kitchen. The rest of the time, you wanted a vending machine that never breaks, and you can have one.