WordPress weekly recap #9: Gutenberg Plugin Compatibility Database and more

Daniel Bachhuber introduced a database that wants to provide information on compatibility with the Gutenberg editor for 5,000 plugins from the W.org directory.




Gutenberg Plugin Compatibility Database

Daniel Bachhuber introduced the Gutenberg Plugin Compatibility Database – a tool with the goal »to identify whether or not WordPress.org plugins are compatible with Gutenberg«, writes Daniel in his post »Introducing the Gutenberg Plugin Compatibility Database«.

That is a great idea because incompatible plugins will – most likely – be the biggest issue with the 5.0 update and Gutenberg. The problem with that: it needs lots of people to test the plugins. The readme file in the GitHub repo from the project contains information how you can help to test plugins. After you created an account, it seems to be a fairly straightforward process, with testing environments that are automatically created via WP Sandbox with Gutenberg and a plugin to test for compatibility installed.

The database lists 5,000 plugins which represent more than 90 percent of the total active installs count.









State of HelpHub

The HelpHub project – where the docs team worked on for some time now – aims to replace the Codex as user documentation (the current state can be seen on wp-helphub.com). It will live under wordpress.org/support, and its goal is to help users help themselves before they post a question in the support forums.

The team wants to release a minimum viable product (MVP), a phase 1, that should bring the following (quoted from Jon Ang’s article »State of HelpHub February 2018«):

  • better content.
  • internal search.
  • improved readability through design and content re-writes.
  • better article discovery through better categorisation.
  • REST API endpoints.

It is planned to release this MVP on May 31 or earlier. To get this done, the team needs help from developers, content migrators, and editors.

More on that, how you can join the team to help, and the planned features for phase 2 can be found in Jon’s post.


Paying for reviews is not allowed

Mika Epstein wrote a post »Reminder: Paying for reviews is a guideline violation« where she reminds the fact that paying for plugin reviews is prohibited.

It the team notices that a plugin dev pays for reviews, they will remove all reviews from that time frame. If it happens again, the plugin author will lose his plugins. More on that in her post and a few clarifications in the comments below it.





- »Two Factor Authentication on WP.org«. During testing it is only rolled out for super admins and core committers.





From the WordPress.org blog

Leave a Reply

Your email address will not be published. Required fields are marked *