In reply to Hozefa.

I’ve used the block editor many times. I just don’t like working slower.

It’s very rare for me to change headers/footers, or rebuild sites after I built them the first time. I follow a design system so that just isn’t needed.

I also know that blocks (and themes) need accessibility corrections, which is extremely painful with Gutenberg. I can’t wait for WordPress to finally get around to updating bugs years later – like the lang attribute still being wrong after nearly 20 years.

The php anywhere block is bad security practice and subject to RCE vulnerabilities.

We have our own design system based on Bootstrap. Every component was created long ago. Everything works better across more devices, it’s more accessible and more portable. This also allows components to be used on non-WordPress sites, social media, marketing materials, etc. Helping unify brand identities across web properties.

Folks who are not designers/developers/webmasters have extreme issues using the block editor because of the learning curve. A 70-year-old veteran that takes care of a local non-profit org’s website that updates a handful of times a year can’t remember how to use it – while the classic editor doesn’t have that issue. They also never update headers/footers or use the site builder – for obvious reasons.

Publishing 1,000’s or 10,000’s of articles via the block editor is 5-10x more clicks for each article, and waiting for the preview to render is an extreme amount of lost time. For businesses with 100’s of active sites, or even a single client, that’s wasted time, thus money.

WordPress is now shirking in market share. They should have focused on converting core to PHP 8 because of the massive speed/performance increases…instead of a page builder nobody asked for. Heck, an easy-to-use e-commence experience built into WordPress would have been better for them – at least people were asking for that.