Hacker News Reader

Comment by dpwm | Hacker News Reader

As you rightly point out, WordPress has a sweet spot of providing control over content to the customer.

The problem I see is that, in many instances, WP is pushed by dodgy developers running a template for what is a static site. This is easily the case for 90%+ of the small business sites I see. Many are never changed.

WordPress is a much larger attack surface than static hosting. There are fairly obvious ways of automating using WordPress to generate a static site that will be faster and more secure. I believe this is generally referred to as headless WordPress. Why does this not happen more – or do I just not see it when it does?

View on HN

Did you ever do web development for customers? You build the website (10% of the work), and then the rest comes.

"Can you put our holidays on the main page?", "Can you adapt this text?", "We have a new image of our main shop, can you update it?", ...

I've seen plenty of people building a website for someone and thinking they made good money, but after all the requests that come afterwards, it's not worth the time.

On the flip side, I've also seen Wordpress specialist consultancies grow large businesses out of this inevitable influx of change requests and the revenue that comes with it.

These consultancies strike the right balance in terms of knowing their product, managing expectations, and knowing when to say "no".

It's created lots of jobs in South Africa for what that's worth. Can't speak for other countries.

> It's created lots of jobs in South Africa for what that's worth.

WooCommerce began as a plugin by a wordpress theme company in South Africa (WooThemes). And then they were aquired by WP/Automattic in ~2015. A really cool case of pivoting.

Last two WP updates I did were essentially downloading the site with firefox's "save site as", running prettier on it, and setting up a basic netlify for what's now a static site. HN is quick to talk about "the right tool for the job" about WordPress, but WP also has great branding which often makes it the choice when it's _not_ the right tool.

imho the best part of WP is the dashboard stuff, so headless WP is a good choice. It's also frequently hurt by PHP's heavy push on inheritance, which can be at-odds with what is actually a very good events-based architecture in WP. Sad part is that the very good events-based architecture is so overlooked, most people who have spent time developing in WP aren't even aware it has events.

If you're talking about WP hooks, basically every single decent WP developer has not only heard about them, but uses them extensively.

Maybe, but what percentage of those branding themselves "WP Developer" are decent? I've had to unravel a fair number of plugins where they'd crammed everything behind a single action , or under one big theme.

Reply on news.ycombinator.com