What future for Cp

[james]

@wvpalarao

A roadmap for the list of confirm feature from petition is a good start.

We’ve started working on a roadmap and you can expect that to be posted on the main ClassicPress site soon.

We still have a lot left to do for ClassicPress version 1, but we are also thinking about and planning for the future.

Here are some more specific thoughts about what will go into version 2: Longevity for CP - #17 by james

@DerpFox

Also the only thing I could personally petition is for a build in sitemap generator or if not possible an official plugin.

Please do, as we’ve mentioned here, community contributions are a vital part of our future direction.

@DerpFox

What do you plan for the future of the editor?

We are taking a very long-term view of any improvements here. Start by reading the following petitions:

• GitHub · Where software is built
• GitHub · Where software is built

These are common patterns that appear on almost every site that uses WordPress as a CMS. With these low-level APIs (and more) baked into the core software, plugins will be free to innovate at new levels based on a tested, proven foundation.

Also, adding new low-level APIs this way that extend what is already there instead of replacing it will not break existing sites, by definition.

The rest is up to you (plural, our community of users). You’ve asked us what we’re going to build; now I’ll ask you: what would you like to see in a CMS?