WordPress Wasn’t Hard. It Was Just Never-Ending #6

When people talk about WordPress, they often describe it as difficult.

After spending time building my own site, I don’t think “difficult” is the right word.

The better word might be “never-ending.”

I started this project knowing almost nothing about WordPress. I wasn’t comparing hosting providers, debating server architectures, or carefully planning every detail.

I simply followed a recommended path, launched a WordPress site on GCP, and expected that most of the hard work would be getting the website online.

The website went online surprisingly quickly.

That was when the real project started.

Every Task Created Another Task

At first, I wanted a secure website.

So I set up SSL.

Once SSL was working, I noticed the menus looked messy.

After fixing the menus, I started thinking about categories.

After organizing categories, I became distracted by the homepage.

Then the mobile version looked different.

Then I started adjusting CSS.

Then I discovered caching.

Then I started thinking about site structure.

The strange thing was that none of these tasks were particularly difficult on their own.

The problem was that they never seemed to end.

Every time I crossed something off the list, WordPress quietly added something else.

The Site Was Never “Finished”

I kept reaching moments where I thought:

“Okay, now the website is finished.”

A few days later, I would find another problem.

Sometimes it was technical.

Sometimes it was visual.

Sometimes it was simply an idea that made me rethink what I had already built.

The website always seemed to be one step away from completion.

And somehow it never arrived.

WordPress Is Full of Decisions

One thing that surprised me was how many decisions WordPress requires.

Not major decisions.

Small ones.

Which categories should exist?

How many menu items are too many?

Should the sidebar appear before or after recent posts on mobile?

Which plugins are actually necessary?

How should articles be organized?

None of these decisions will make or break a website.

But together they consume a surprising amount of time and attention.

Sometimes I spent more time thinking about the website than actually writing for it.

The Real Challenge Was Consistency

The technical side wasn’t what slowed me down.

The real challenge was returning to the site again and again.

There was always another adjustment to make.

Another article to write.

Another small improvement that felt important.

At some point, I realized WordPress wasn’t a project that could be completed.

It was something that would continue evolving as long as I kept using it.

What I’m Trying to Do Now

These days, I’m trying to resist the urge to fix everything.

The website works.

The menus work.

The categories mostly make sense.

The design is good enough.

Instead of endlessly polishing the site, I’m focusing on publishing more content.

That feels like a better use of time.

At least for now.

Final Thoughts

Before I started using WordPress, I assumed the biggest challenge would be getting the website online.

Looking back, that was probably the easiest part.

What I didn’t understand was how many small decisions and adjustments would follow afterward.

WordPress wasn’t difficult because of one big obstacle.

It was difficult because there was always something else to do.

And maybe that’s just part of running a website.