WordPress has shifted to a plugin-first policy. Canonical plugins are being touted as the way to develop new features while keeping the WordPress core lean and fast. Canonical plugins are developed by the company's team rather than by third parties. Plugins will be used as an alternative to adding new features directly to WordPress, requiring users to disable features they don't need. But some users dislike the change. One argued that a plugin approach is more complicated than having simple optional features. Another said the change would make it harder to gather user feedback.

Key Takeaways:

  • Some contributors, such as Jon Brown feel as though canonical plugins may potentially make development more complicated.
  • Since canonical plugins require more maintenance, those who perform this maintenance have reservations about how time-consuming it will be.
  • Some are concerned that consumers will find it difficult to report useful feedback, leaving developers in the dark on what's working and what's not.

“Matt Mullenweg, the developer of WordPress and CEO of Autommatic, proposed no longer adding new features to the WordPress, pivoting instead to a plugin-first policy.”

Read more: https://www.searchenginejournal.com/wordpress-plugin-first/465954/