Why I Left WordPress and Built My Own CMS

On 14 November 2026, zacdrayson.com stopped running on WordPress. It now runs on a small, custom-built CMS written in PHP with a single SQLite file as its database. The site looks almost exactly the same (I kept the Multinews look), but everything underneath it is different. This post covers why I did it, what changed, and what I learned.

Why move away from WordPress?

WordPress is a great piece of software, and it has powered this site for years. But my needs have narrowed while WordPress has kept growing. A few things kept nagging at me:

1. I was running far more software than I needed. My site is a blog, some pages, a few photo galleries and a handful of comments. WordPress, a theme, and a stack of plugins is a lot of moving parts for that. Every plugin is code I didn't write and don't fully understand.

2. The update treadmill. Core, theme and plugin updates arrive constantly, and every one is a small gamble. Skip them and you risk security holes. Apply them and you risk breaking something. I wanted a site where I decide when things change.

3. Security surface. Popular software gets attacked constantly. A smaller, purpose-built codebase with only the features I use has far less to attack, and spam, trackbacks and bot noise have a much harder time reaching it.

4. Weight and speed. A MySQL database, a PHP framework, plugin hooks and a big theme all run on every request. For a personal site that's overkill. I wanted pages that are fast by default.

5. Ownership and simplicity. I wanted to be able to open any file and know exactly what it does. I also wanted the entire site, content included, to be easy to back up and move. With SQLite, the whole database is one file I can copy in a second.

6. Third-party services I didn't want. Jetpack handled subscribers and stats, but it also tied my site to an external service. Moving off it was part of regaining control.

What I built

"Drayson CMS" is a deliberately small PHP application:

  • SQLite for all content: a single file instead of a MySQL server.
  • Same URLs as before. Uploads still live under the same paths, so old links and images keep working.
  • Same look. The old-style theme was recreated so visitors see continuity rather than a redesign.

What came across

The migration was a proper import, not a rebuild from scratch:

  • 50 published posts and 16 pages
  • All media and uploads
  • 31 approved comments
  • 3 photo galleries
  • The menu, widgets and homepage layout
  • Draft, pending and private content, kept unpublished

What I left behind on purpose: spam comments, trackbacks, and Jetpack's subscriber list and stats. A migration is a good chance to leave the clutter behind.

Going live

The cutover went in stages, and I took backups before every risky step:

  • A full copy of the old WordPress files and a MySQL dump, kept safe in case I ever need to go back.
  • HTTPS is forced everywhere, and the site canonicalises to www.zacdrayson.com.
  • A Cloudflare redirect rule makes the bare domain reach the right place in a single hop instead of two.
  • The temporary test subdomain was removed once I was happy.

Improvements since launch

Since going live I've been making small improvements, which is much of the point of owning the code:

  • Readability tweaks. The base font size is now tuned at 12px for the site, with larger 14px text on login and account pages, the admin bar and the logged-in sidebar box.
  • A flexible widget system. Sidebar widgets are stored in the database and rendered by a simple template. The sidebar currently has a login box, search, and recent posts.
  • A random gallery widget. A new "From the Galleries" widget shows a random 2x2 grid of photos from my galleries, and they open in a lightbox right on the page. It's configurable from the admin panel, including how many images to show.
  • An experiment that didn't make it. I tried embedding my X (Twitter) timeline in the sidebar. Embeds are iframes I can't style to match the site, and fetching posts myself isn't practical without the paid API, so I took it out. Not everything has to stay.

Trade-offs

I don't want to pretend this is a free lunch:

  • I'm the maintainer. No plugin ecosystem, no community support. If something breaks, I fix it.
  • Fewer features out of the box. No marketplace of add-ons. If I want something, I build it.
  • Security is now on me. The attack surface is smaller, but I have to take care of the code I write.
  • It's not for everyone. If you want to run a business site, a shop or a team publication, WordPress is still the sensible choice.

For a personal site, where the content is what matters and I enjoy tinkering, the trade is worth it.

What's next

I'll keep refining the theme and admin tools, and I may add more widgets over time. Because the whole thing is mine, each change is a small, quick step rather than a plugin search.

If you notice anything odd on the site, such as a broken image, a missing page or a link that no longer works, please tell me. Thanks for reading, and welcome to the new zacdrayson.com.

About The Author

Zac Drayson

Zac Drayson is a proud resident of the Central Coast of New South Wales, Australia, where he has spent much of his life building meaningful friendships, pursuing his interests, and navigating the many challenges life has presented. He loves gaming, spending time with friends and going for long drives and out for lots of coffee.

Leave a Reply