Hello WordPress, Again

Some relationships are difficult to explain. You meet, you argue, you learn from one another, you eventually go your separate ways, and years later, through some inexplicable twist of fate, you find yourselves together again.

Mine is with WordPress.

Nearly fifteen years ago, when I was a junior designer, part of my job involved fixing broken WordPress websites. I wasn’t particularly interested in becoming a web developer at the time. I was a graphic designer. I cared about typography, composition, colour, and the peculiar relationship between visual communication and human perception.

But websites kept breaking. And somebody had to fix them.

What began as small adjustments to templates gradually turned into an education in HTML, CSS, JavaScript, and eventually PHP. I learned how websites worked by taking them apart, discovering what went wrong, and figuring out how to put them back together. There was no grand career strategy behind it. Just curiosity, necessity, and the occasional website that refused to cooperate.

WordPress, quite unintentionally, became one of my first programming instructors.

Over the years, my curiosity expanded considerably beyond content management systems. I became increasingly interested in the machinery underneath websites: servers, databases, network protocols, caching, compression, and the extraordinary number of things that happen between someone typing an address into a browser and a page appearing on their screen.

I learned to write my own applications, configure Linux servers, build publishing systems, and develop websites without relying on frameworks or visual builders. Eventually, I started compiling software from source, partly for control, partly for performance, and partly because I find that sort of thing genuinely entertaining.

Some people collect watches. I compile web servers.

Which brings us to GIANI.IO.

I wanted to create a personal publication. A little corner of the internet where I could write about graphic design, typography, technology, music, and whatever else happened to interest me. Nothing particularly complicated. Just a beautiful, fast, thoughtfully designed place for words and pictures.

Naturally, I decided to build the entire thing myself.

I provisioned a server, configured the operating system, and hand-compiled Nginx and PHP. I worked through the infrastructure, making decisions about performance, dependencies, security, and how everything should fit together.

It was enormously satisfying.

There is something wonderful about building software from its constituent parts. You understand what is running, what it depends on, and why it behaves the way it does. The resulting system feels less like a mysterious appliance and more like a machine you assembled with your own hands.

And after putting all that effort into the infrastructure, I had a rather inconvenient realization.

I needed a blog.

Not a revolutionary new publishing architecture. Not an experimental content delivery platform. Not another custom application I would have to maintain indefinitely.

A blog.

A place to write articles, upload photographs, organize categories, and press Publish.

In other words, exactly what WordPress was designed to do.

So, after years of distancing myself from WordPress, I installed it, replacing my custom publishing plans with the very software that had introduced me to web development in the first place.

I laughed.

There was something deeply absurd about hand-compiling PHP and Nginx, carefully configuring a server, and then realizing that the most sensible thing to put on it was WordPress.

But there was also something rather instructive about the experience.

As developers, we sometimes confuse our ability to build something with a compelling reason to build it. We become fascinated by implementation, architecture, and technical purity. We spend enormous amounts of energy solving problems that other people solved years ago, occasionally convincing ourselves that the exercise is justified simply because our solution is more elegant.

Sometimes it is.

Sometimes it isn’t.

A personal publication doesn’t necessarily benefit from a custom content management system. Readers don’t care whether an article is retrieved from SQLite, MySQL, or a collection of carefully organized files. They care whether the article is worth reading, whether the typography is comfortable, and whether the website works.

And the person writing those articles should probably spend more time writing them than maintaining the machinery that displays them.

This doesn’t mean I’ve suddenly become an enthusiastic supporter of everything WordPress represents today.

The ecosystem remains an extraordinary collection of brilliant engineering, questionable decisions, bloated themes, unnecessary plugins, and visual page builders capable of turning a perfectly ordinary webpage into a small infrastructure project.

But stripped of all that excess, WordPress remains remarkably good at its original purpose.

Publishing.

And somewhat to my surprise, the result was fast. My early tests showed page loads around half a second, even with a substantial editorial image dominating the page. That’s not a universal performance benchmark, of course, but it was more than satisfactory for what I wanted to accomplish.

There was no need to reinvent the wheel.

The real lesson, I think, is that experience changes how we define technical competence.

When you’re starting out, knowing how to build something feels like an achievement. Later, knowing how to build it properly becomes the objective. But eventually, you begin to appreciate a different kind of judgment: knowing whether it needs to be built at all.

I still love writing code. I still enjoy configuring servers, inspecting network requests, shaving kilobytes off assets, and understanding every layer of the systems I create. None of that has changed.

What has changed is my willingness to let a perfectly adequate piece of software do its job.

Fifteen years ago, I learned PHP because I had to fix WordPress.

Today, I know enough PHP to realize I don’t need to replace it.

So, hello WordPress. Again.

It’s been a while.

Please don’t break anything.