After the news about the global redesign of WordPress 5.0 many rejoiced and many were very tense. On the one hand, the built-in visual editor will help simplify the work of ordinary users to quickly create websites. But on the other hand, flexibility will suffer, many themes will have to be redone and many plugins will become useless. Since there will be no alternative, and the community does not agree with the release of the new version without the ability to use the old editor, based on WordPress 4.9 a fork of ClassicPress was created, which will develop in parallel with the main WordPress CMS.

ClassicPress is powered by WordPress

Support for the classic content editing interface will be removed from WordPress 5.0, but will remain available as an external plugin. Gutenberg still has a lot of bugs, and with the plugin of the old editor enabled, it is not known how it will be compatible with plugins and themes. This is not very pleasing to the community, for this reason the fork was created ClassicPress.

ClassicPress first version forked 4.9, will be a complete copy of WordPress 4.9 and will remain fully compatible with all WordPress sites. ClassicPress 1.0 plan to maintain for at least two years, releasing updates to fix vulnerabilities and bugs.

With the release of the second version of ClassicPress 2.0 it will be a separate full-fledged engine without the use of Gutenberg, without linking to the React.js library

Who has already tried to update WP on ClassicPress write reviews, how do you like it and how good or bad everything is.