My personal view por ClassicPress is to stick to the roots and the name:
Classic + Press
WordPress started as a normal CMS and has evolved over the years into an amazing CMS.
ClassicPress was born because WordPress reinvented itself into something new.
The essence of ClassicPress is: “stick to what was, and make it better”
So, my keypoint views are:
- Don’t add more Plugin Territory stuff to core. Core is already great.
- Execute the plan with Core Plugins, which basically means: add an on/off switch to certain features.
- Focus on improving core security and performance.
- Focus on growing a strong and independent Plugins/Themes directory.
Details about the meaning of Core Plugins:
A Core Plugin is not about creating new plugins for ClassicPress. Core Plugin means: “take a piece of the Core, and convert it into a plugin, so that it can be enabled or disabled”.
Core Plugins will not affect performance in a negative way. Running a plugin or running core code is the same thing. It’s the same code running when you request a page. The only effect this may have on performance is positive, for those cases where a certain Core Plugin is disabled, since that specific code will not run.
A direct consequence of executing the Core Plugins project is, we will have to come up with a solution for Plugin Dependency which, in fact, has to be added to the Core, so that any plugin can rely on any Core Plugin and we can guarantee that nothing will break.