Why I Left WordPress
For many years my websites ran on WordPress. Like millions of other people, I did not choose it because I loved it. I chose it because everybody used it, because my hosting company offered it with one click, and because there seemed to be a plugin for everything.
This chapter is about why I stopped, and why I think you can stop too, even if you have never written a line of code.
Goal
By the end of this chapter you will know:
- what is really behind the everyday trouble with WordPress,
- what a website actually needs, and what it does not need,
- what this book will help you build, and what you need for it.
The day my sites were gone
One day my WordPress sites at my hosting company were simply gone. I had not deleted them. They had been removed on the provider's side, and with them the texts, the menus and all the small settings I had collected over the years in a dozen plugin screens.
The worst part was not the loss itself. The worst part was the realisation that I had never really owned these sites. My texts lived in a database I had never seen. The layout lived in a theme somebody else maintained. Half of the features lived in plugins from companies I did not know, many of them asking for a yearly subscription. If any one of these pieces disappeared, my site disappeared with it.
I could have set everything up again. Instead I asked myself a simple question: what does a website actually need?
What a website needs
Look at the website of a bakery, a yoga teacher, a musician or a small association. It has:
- a few pages with text and pictures,
- a menu and a footer,
- maybe a blog, a list of dates, a contact form,
- maybe a small shop.
That is all. None of this needs a database. None of this needs a programming language running on every page view. None of this needs an admin area that must be updated every few weeks because somebody found a new security hole in it.
WordPress was built in 2003 as blogging software. Over twenty years it grew into something that can do almost everything, and that is exactly the problem. To show a page with three paragraphs and a photo, a typical WordPress site starts PHP, opens a database connection, loads the theme, loads every active plugin and asks the database a few dozen questions. Every one of these parts can break, and every one of them can be attacked.
The plugin trap
The real trap is not WordPress itself. It is the plugins.
You want a contact form: install a plugin. A newsletter: another plugin. A calendar: another one. A shop: a big one, and then several small ones to make the big one work in your country. Each plugin:
- comes from a different author,
- has its own settings page, its own style and its own update cycle,
- may stop being maintained at any time,
- may want money every year,
- runs with full rights inside your site.
The last point matters most. A WordPress plugin can do anything: read your database, send mail, change other plugins. When one of them has a security hole, your whole site has it. This is why WordPress sites get hacked so often. Not because WordPress is badly written, but because a typical site runs code from twenty or thirty strangers, all with the keys to the house.
And then there are the updates. You log in after a few months, and twelve plugins want to be updated. You click "update all" and hope. Sometimes the site breaks, and you spend an evening finding out which of the twelve was guilty.
A different way
When my sites were gone, I started over with a few rules:
- My texts belong to me. They live as plain text files that I can read, copy and keep, not in a database.
- Every change is saved forever. If I break something, I can go back to yesterday.
- No admin area to defend. There is no login page for strangers to attack.
- Features are built in, not bolted on. A contact form or a calendar is part of the system, written and tested together with everything else.
- I describe what I want, and the AI builds it. I am an artist and a writer. I want to spend my time on content, not on settings screens.
Out of these rules came ForgeCMS. It is a small program that turns text files into a website. It has no database, no PHP and no plugins in the WordPress sense. Everything you will read about in this book is part of it: blog, contact form, newsletter, events, shop, payments, courses, and more.
The fifth rule is the one that makes the difference for you. Ten years ago a system like this would have been something only for programmers, because somebody had to type all the files. Today you can tell an AI assistant like Claude what you want, in your own words, and it writes the files for you. The files are simple enough for the AI to get right, and simple enough for you to read and check.
Not only for me
The first person other than me who built a site this way was Angela Mahr, a musician. She is not a programmer. She sat down with Claude, described what she wanted, and built her music website, music.angela-mahr.de, by herself. Then she built a second one, lebe-dich.info. When she wants to add a concert date or change a text, she tells the AI, or she edits the text file in her browser.
That is the experience this book wants to give you.
What you need
- A small server. A rented Linux server (a "VPS") costs a few euros a month. In chapter 3 we will rent one together. I will use IONOS as an example, but any provider works.
- An account for an AI assistant. This book uses Claude Code from Anthropic. It runs on your server and does the technical work for you.
- A free Codeberg account. Codeberg is where your texts will live, with every change saved. Think of it as a safe for your website, run by a non-profit in Germany.
- Optional: your own domain, such as
mybakery.com. You can start without one.
You do not need to know programming, HTML, servers or WordPress.
What this book covers
- Part I (this part) explains why and how ForgeCMS works the way it does.
- Part II builds your website, from renting a server to your first change six months later.
- Part III walks through every module: blog, contact form and newsletter, events, feature requests, shop with card payments, payments in Ğ1, a community market and online courses. It also explains which parts are free and which cost a small one-time licence, and why.
- Part IV looks beyond: plugins you describe to the AI yourself, moving your old WordPress content, and the path without AI for those who are curious.
Pitfalls
- "I will just move my old site 1:1." You can, but it is a good moment to ask which of your thirty plugins you really need. Most sites need three or four features, not thirty.
- "I need an admin area like WordPress." You will be surprised how little you miss it. Texts are edited in the browser on Codeberg, everything else by asking the AI.
- "This is only for techies." It was, a few years ago. The whole point of this book is that it is not anymore.
What you learned
- WordPress problems mostly come from the database, the admin area and above all from plugins that run with full rights.
- A typical website needs pages, a menu, and a few features. None of this needs a database.
- ForgeCMS keeps your texts as files you own, saves every change, has no admin area to attack and builds the features in.
- You describe what you want, and an AI assistant writes the files.
In the next chapter we look at how ForgeCMS thinks: where your texts live, how a page is built, and why a typo never takes your site down.
