
Performance Team Proposes Enabling WebP by Default in WordPress 6.0
…Full post on WP Tavern
Read Full
…Full post on WP Tavern
Read Full
Elastic has resolved a trademark infringement lawsuit related to usage of the term “Elasticsearch.” Amazon has agreed to drop the term from its product line. “We believe this resolution will remove confusion in the marketplace and provide much-needed clarity to our community and customers,” Elastic CEO Ashutosh Kulkarni said in the announcement. “There is only…
WordPress design contributors are cooking up a new idea for this year’s default theme release that would put the spotlight on style variations instead of the theme itself. The idea is rooted in comments that Twenty Twenty-Two designer Kjell Reigstad made last year when introducing the theme: Themes are in a transition period today, and…
Last month, the plan for WordPress to generate WebP images by default for new JPEG image uploads was put on hold for the upcoming 6.1 release after objections from lead developers. The original proposal had been merged into core at the end of July, despite significant critical feedback and concerns from WordPress’ developer community. Yesterday,…
In December 2022, the ClassicPress community voted on whether to re-fork WordPress or continue on with the project as-is. As WordPress continues to evolve, ClassicPress fell behind in pursuit of PHP 8+ compatibility. The fork is based on WordPress 4.9 and users are increasingly limited in what plugins will work with the five-year-old codebase. In…
Gutenberg 11.0 landed yesterday with a pile of changes. The development team has been moving fast, and it shows. For a two-week cycle, version 11.0 includes an insane number of bug fixes. Contributors squashed over 70 in this release alone. This seems to be in preparation for WordPress 5.8, which is expected to land on…
This is the concluding article in a series I’ve been writing on accessible web experiences. In the first article, “Why Do We Develop Accessible Web Experiences?” I discussed the “why” of accessible digital design. In “Building a Better Blueprint,” I covered creating personas, user journeys, sitemaps, and wireframes consistent with universal design principles. In “ARIA:…