Tom Hirst makes a business case for headless WordPress. 💼
Tom rightly notes that a business "has to be comfortable at the bleeding edge of web technology," but if you're not ready today, good news — "if you start with traditional WordPress, you can switch to headless WordPress at a later date."
I'm confident headless will find its place with developers in the right situations, and another way of working with WordPress is a definite win. I can't wait to learn and share more about it.
(At the same time, I agree with this remark from Chris Lema on Twitter too.)
We have a clarification for the item we reported last week regarding accessibility issues people were having with some recent changes to WordPress.com. We linked to a post where Deborah Edwards-Onoro explained how to enable the Classic Editor for WordPress.com sites. Then we noted a communication from Automattic's public relations team about a blog post they had published about these changes.
What we missed is how — according to the publish dates on both Deborah's and Automattic's posts — the announcement from Automattic came a day after Deborah's post. I want to take a moment to apologize to Deborah if it seemed that the official blog post announcement existed at the time of her post. Apparently, it didn't, so she and other people reacting to the changes at WP.com didn't miss it. After closer examination, the official announcement (at least on the blog) came the following day, and this seems to have happened after the changes impacting accessibility had already gone live.
I have been told there was an announcement in the WP.com app as well, but for an announcement to go up on a blog a day after the changes it concerns had already been live would explain the confusion.
As I mentioned last week this does prove that a significant need exists for the Classic Editor, including those who need a more accessible tool than the block editor if a delay of only one day is disruptive to them.
Renato Alves explains why GraphQL and WordPress work well together:
"...to author a GraphQL API you only need a one-time effort.... and another advantage of using GraphQL is its ease of integration with multiple data sources."
There are some downsides, however. There are some "rough-edges" (like caching), access control, and a "steep learning curve." Migrating completely to GraphQL without understanding its risks would be a bad mistake.
🔌 Iain Poulson noted in a recent WP Trends newsletter that he has started working on a new acquisition analytics feature for Plugin Rank:
"Find a free plugin on the WordPress.org repository that has a good user base but hasn’t yet been monetized. Acquire it, improve it and add a premium offering... But the problem is finding these plugins."
Allison Rivers reviews three Gutenberg block plugins for WooCommerce stores:
- ProductX's Gutenberg WooCommerce Blocks, which extend the basic WooCommerce block options;
- Toolset's WooCommerce Blocks, for more extensive customizations;
- The core blocks built into WooCommerce.
If you or your clients use Kaswara Modern WPBakery Page Builder (10k+ installations), then you might want to uninstall it when you can. Wordfence is reporting a critical zero-day vulnerability.
And if you use Elementor, make sure it's updated. A vulnerability was discovered last month, and more recently some third-party Elementor plugins received security patches too. Collectively these vulnerabilities affect millions of websites. 🔒
📆 Upcoming Events
|