We've had a roadmap page on concrete5.org for awhile. It's generally been a high-level affair, with us sharing some general thoughts about the direction of the platform. But it's hardly been the specific, granular roadmap that people have been looking for. That's going to change today.
What's so great about new concrete5 anyway?
You’ve heard us talk about it, and it’s still bumpy in parts, but we’re eager to hear your feedback as you tinker around with Express in version 8 of concrete5.
Got a bunch of related websites you’d like to share some content between? Wrestling with some complex workflow issues around many editors managing a franchise group, dealer network, political organization or district of websites?
We’d love to hear from you.
concrete5 has always made it easy to manage content on your website. With version 8 we’re adding features to help a group manage a larger web presence and more complex online applications.
Version 8 includes lots of new features. Here's a few of the bigger new features you should know about:
In the latest "Lunchtime Learning" session, concrete5 CTO Andrew Embler leads the Core Team through the long-anticipated and much-overhauled Advanced Permissions features in concrete5.6. Inside, you'll find an incredibly powerful, flexible system built to manage just about any scenario you might encounter on a large concrete5 site.
Ryan just posted the current development version of the wordpress site importer to github:
When this is ready for showtime it'll be a free add-on.
This was originally written by ScottC, then GregJoyce picked it up at concrete5. It's status is described in the README in the code, but it basically works, even with really large imports, but it's formatting is a bit rough and the data that's imported is not complete.
If anyone has energy to put into it it'd be much appreciated.
Versions of concrete5 feature rudimentary anti-spam tools, including an IP ban-list and captcha support, but no unified settings page for managing these items. Furthermore, there is no support for any captcha besides the SecureImage library, which is a bit long in the tooth (and somewhat ineffective), nor is there any support for a third party anti-spam service like Typepad Anti-Spam or Akismet. We would like to change this in concrete5 5.5.