|
|
|
|
This week in WordPress
|
|
Matt Mullenweg is not a fan of Jamstack, ignites rivalry with tech CEOs
|
|
|
Matt Mullenweg and Jamstack community leaders have "forged a new rivalry" over the past two weeks, writes Sarah Gooding for WPTavern, after the WordPress co-founder and Automattic CEO told The New Stack he sees Jamstack as a "regression for the vast majority of the people adopting it."
|
|
|
|
Matt clarified his original Jamstack Remarks at the Tavern while also doubling down on his original comments, saying "there isn't a vast number of people adopting Jamstack in the first place, and those who do are probably fully aware of the tradeoffs."
|
|
|
|
Matt believes WordPress provides a better experience for users in terms of performance, security, scaling, and developer experience. But as Stackbit co-founder and CEO Ohad Eder-Pressman points out, web technologies have to start somewhere.
|
"Matt Mullenweg is having a go with the Jamstack community. Honestly, the team at WPTavern is doing a better job than I will digging into all the details, so go check out their great write ups," says Brian Krogsgard in the latest Post Status newsletter.
|
|
|
|
|
|
|
W3C drops WordPress, opts for more "accessible" CMSs
|
|
|
Sarah reports that Studio 24, the digital agency chosen for the redesign, has cited Gutenberg, accessibility issues, and the fact that the Classic Editor plugin will stop being officially maintained after 31 December 2021 as its main concerns. Coralie Mercier, Head of Marketing and Communications at W3C, tells the Tavern the agency has concerns about the longevity of WordPress "as we use it."
|
"Hey @w3c not choosing WordPress is fine, but at least don't choose a proprietary CMS… 😒" tweets WordPress Core Team rep and WHODUNIT CEO Jb Audras.
|
DIYthemes owner and Thesis creator Chris Pearson tweets, "A more honest headline: W3C drops WordPress from consideration because of concerns over Gutenberg. FULL F'ING STOP. I predicted this in December 2018." Meanwhile, anonymous Tom comments on Tavern's post, "Thanks for the heads up about the Classic Editor going away…"
|
|
|
|
|
First look at Twenty Twenty One default theme
|
|
|
So, what else is going on? "Well, friends, it's time for what I'm sure you've all been waiting for: an announcement about the next WordPress default theme!" writes Automattic designer and WordPress 5.6 Default Theme Design Lead Mel Choyce-Dwan, introducing Twenty Twenty-One with some stunning visuals.
|
|
|
|
A top-notch team of contributors is working on the default theme. As well as Mel, the team includes Elma Studio co-owner Ellen Bauer, freelance developer and Theme Team rep Carolina Nymark, and long-time front-end developers Beth Soderberg and Jessica Lyschik.
|
Mel describes Twenty Twenty One as "a blank canvas for the block editor" adding once the theme is stable after the first beta, the team will start exploring full site editing support.
|
"The new WordPress default theme in 5.6 brings us some block-centric pastel cottagecore goodness," tweets GoDaddy Pro Senior Community Manager Andy McIlwain.
|
|
|
Automattic now offsetting data center power emissions produced from non-renewable sources
|
"At @automattic (and that also means @WordPressVIP), we now offset our data center power emissions produced from non-renewable resources. This means our services contribute net zero carbon emissions. It's a step," tweets Nick Gernert, head of WordPress VIP.
|
Meanwhile, freelance WordPress developer and Green Tech South West co-founder Hannah Smith tweets: "🙌🏼 Delighted to see wordpress.com realise that powering data centers with renewable energy, or offsetting emissions if that's not yet possible, is a vital thing to do. Now I wait with baited breath to see if another big #WordPress player, @wpengine, will follow suit 🧐."
|
|
|
|
|
|
|
In other news...
|
|
- – ICYMI, embedded Facebook and Instagram posts in WordPress sites will soon stop working. Facebook recently announced all oEmbed requests for Facebook and Instagram content will be deprecated on 24 October. In response, as Automattic technical account engineer and Core Security team release lead Jake Spurlock explains, WordPress will be removing Facebook and Instagram's oEmbed endpoints from WordPress Core code, probably in the 5.6 release. Gutenberg 9.0 recently removed support. WPTavern reports that WordPress contributors are debating whether to push a dashboard notice to warn affected users.
- – Wordfence is urging users of XCloner, a free plugin installed on 30,000 sites, to update to the latest version. Threat analyst Chloe Chamberland says the security company recently discovered several critical flaws in XCloner that could lead to remote code execution on a vulnerable site's server. The plugin's developers have since patched the issues.
- – Automattic mobile engineer and WordPress Mobile team member Maxime Biais has published a proposal for discussion, recommending dual licensing Gutenberg under GPL v2.0 and MPL v2.0. The proposal comes after Matt Mullenweg mentioned at a Q&A session at WordCamp Europe 2020 that Gutenberg contributors were considering dual licensing for embedding Gutenberg in mobile apps, along with the requirement that they would need to get an agreement from all contributors, reports WPTavern's Sarah Gooding.
|
|
|
|
|
Not subscribed? Join the most conversational weekly email in the WordPress community!
|
|
|
|
|
|
|
|