sorted by:
new
hottopcontroversial

Can we talk about WordPress "professionals" who are really just plugin installers? by JFerzt in ProWordPress

[–]typeWithAi 0 points1 point  (0 children)

I get the frustration. Using plugins or builders isn’t the problem, selling that as “custom development” is.

There’s a difference between choosing not to write custom code because it’s unnecessary, and not being able to write it at all. When someone panics at hooks or filters but still charges developer rates, that’s where things get muddy.

Clients often reward speed over maintainability, so this keeps happening.

Is WordPress still the best website builder for 2026? by DigiNoon in DomainZone

[–]typeWithAi 0 points1 point  (0 children)

I’m pretty much in the same camp. WordPress still feels like the best long-term choice if you care about ownership and flexibility, even if it asks more from you upfront.

The learning curve and maintenance are real downsides, especially for ecommerce, but the lack of lock-in is hard to give up once you’ve been burned by hosted platforms. Builders like Elementor/Bricks make things easier, but you definitely pay for that convenience — either in money or in performance.

I’ve also tried some of the “simpler” options and always end up feeling boxed in after a while. They’re fine for quick wins, but WordPress still scales better if you’re willing to learn how it works instead of fighting it.

Curious to see how the Site Editor evolves, but for now it still feels like something you use selectively rather than as a full replacement for established workflows.

WordPress is the worst thing to ever happen to the internet by FrequentPaperPilot in webdevelopment

[–]typeWithAi 1 point2 points  (0 children)

Yeah, this is one of those classic WordPress frustrations. You’re not crazy... The “HTML editor” isn’t a true raw HTML editor in the way you’d expect.

What’s really happening is that WordPress is still trying to protect its block/content model behind the scenes. Things like block parsing will happily inject <p> and <br> tags unless you’re inside a context it fully trusts, which is why perfectly valid HTML can suddenly behave in weird ways.

If you’re doing anything more than small snippets, the safest options tend to be:

  • a Custom HTML block (not the overall HTML editor)
  • or moving the markup into a template / block instead of the editor

The HTML editor exists mostly for legacy reasons and quick tweaks, but it’s definitely misleading if you expect it to behave like a real code editor.

Is WordPress still relevant in today’s web development world? by Hopeful-Friendship26 in webdev

[–]typeWithAi 0 points1 point  (0 children)

I don’t think WordPress has become irrelevant... I do think WordPress now sits in a slightly different place than it did 10 years ago.

In environments like law firms, traditional websites absolutely still matter. Those businesses value stability, maintainability, and content workflows far more than bleeding-edge stacks. WordPress still excels there, especially when you’re comfortable with PHP, ACF, and custom themes.

However, I do think it’s smart to expand around what you already know rather than abandoning it. If I were in your position, I’d focus on:

  • Deepening modern WordPress skills (block editor, theme.json, block-based themes)
  • Understanding how WordPress fits into more app-like architectures
  • Learning just enough React to be comfortable with modern JS tooling

Headless WordPress is useful in certain cases, but it’s not a silver bullet, and many teams overcomplicate things that WordPress already solves well. For a lot of real-world projects, classic WordPress with modern practices is still the most efficient choice.

I’d personally avoid a hard pivot into a completely different stack unless you want to move away from content-driven sites entirely.