WordPress Revisits Canonical Plug-Ins - Get Website AMC

WordPress Revisits Canonical Plug-Ins


With changes in Google and social media’s algorithm along with changes in consumers’ behaviour patterns, discarding and upgrading features for platforms have become an industry trend. 

Along with changes in Instagram, YouTube, Google, and Facebook among other digital channels of content, WordPress, the world’s most popular content resource management system has also decided to evolve. 

WordPress creator and CEO Matt Mullenweg recommended switching to a plugin-first philosophy in place of no longer introducing new functionality to the platform. This was recommended in the Canonical Plugs Revisited blog. 

Here’s what he states: 

“I believe we should build on the success of canonical plugins like MP6, Gutenberg, and REST API to have more community-developed plugins that share the ethos and approach of WordPress itself but to a more niche area that might not be appropriate for the core. These plugins are called canonical because they will be the official first-choice recommendation by core and w.org for an area.”

Canonical plugins are a method for creating new functionality in the form of plugins that were first explored in 2009. This strategy aims to maintain the WordPress core’s speed and efficiency while also promoting the creation of experimental plugins. 

What’s In It For The End Users? 

Canonical plugins would be those that are built by the community (many developers, not just one person) that provide the most often requested functionalities with excellent implementation. That is why canonical plug-ins are said to offer a way to keep improving the publisher user experience on a faster schedule. 

The plugin code would be safe and the best possible example of coding standards since there would be a very strong interaction between the core and these plugins, and future versions of WordPress would be evaluated against these plugins before being released to assure compatibility. 

The WordPress philosophy known as Decisions, Not Options, which attempts to avoid burdening users with layers of technical options, might be considered as being in line with the plugin-first approach. 

A user won’t have to wade through enabling or removing functionalities they need, don’t require, or don’t understand by offloading various features and functionalities to plugins.

What’s The Verdict? 

WordPress development is advancing to bring about changes more quickly. According to core contributor comments, there are still a lot of unanswered issues regarding how effectively this system will function for consumers. 

What transpires with the cancelled WebP capability, which was originally planned to be integrated into the core but will now become a plugin, will provide an early indicator. 

Leave a Reply

Your email address will not be published.

%d bloggers like this: