It is that time of year for closure, and that means a lot of looking back and forward. Many people are already doing their personal reflections and reviews of 2019. We are moving into the future, and in 2020, something entirely new is going to happen for the project. For the first time, the committee […]
Just over one year ago ClassicPress was started by Scott. Today, we have ClassicPress V1 out in the wild, are working hard towards V2, and are continuing to see our community grow. With the one year mark we are excited to announce a new website for ClassicPress.
ClassicPress has, and always will be, a community-led project. My goal from the outset was to create a structure where democracy rules and no single person could change the direction of ClassicPress without oversight and checks and balances.
Since ClassicPress began in August of 2018, our all-volunteer team has worked hard to bring ClassicPress to you. Today, we are pleased to announce the first official, stable release of ClassicPress: version 1.0.0, codenamed Aurora.
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
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.
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.
