This month, we will celebrate six months together as an organization. It’s been a very busy six months! In addition to preparing for the launch of ClassicPress v1, we have been laying a firm foundation within the organization that will serve us well as we grow.
One of the most common support questions we get lately is regarding choosing languages in fresh installs of ClassicPress, and we hear you! Let’s break down how we got here, how you can help and what you can do if you want to use an untranslated language.
the short answer to the question is YES! You might be wondering why ClassicPress is still in BETA if this is the case. The answer is simple — there are a few things we need to do before launching v1
Every line of code, every graphic, every support reply on the forum and every contribution is completed by a volunteer working for free. Without the kindness, support and hard work of volunteers, ClassicPress would still be a concept.
It is with great pleasure that we announce the BETA release of ClassicPress. Please help us spread the word about the BETA and, most importantly, please try it out in a test environment for your current websites.
It is with great pleasure that we announce the addition of Michelle Coe (Creative Director and Owner of BlueSkyPhoenix LLC) to the founding committee of ClassicPress.
While ClassicPress has already moved well beyond what we don’t want and is prioritizing features to ensure that the software is powerful, versatile, and predictable, one particular aspect of Gutenberg is currently causing particular consternation and controversy.
With Gutenberg, WordPress emphatically reaffirmed its commitment to its original purpose of democratizing publishing. ClassicPress respects their decision, and has resolved that it will dedicate itself to improving and strengthening its features for business sites.
We’re extremely excited to announce the first alpha release of ClassicPress, codenamed Sunrise. This launch has been a work of sheer dedication, a sprinkling of love, a dash of frustration and a large helping of teamwork, collaboration and enjoyment.
We think that for the time being (two years at least), big players in the plugin and theme space will want to keep backward compatibility. As long as the Classic Editor plugin is being “promoted” as an alternative, these plugins should remain working.
