Last year proved to be a big one for the growth of dotCMS. The R&D team doubled down on making the platform more performant, secure and easier to use, with more than 600 improvements made across nine releases. A few of our big accomplishments included:
And that’s far from all; we’ve also added new templating features, headless widgets capable of outputting JSON, a built-in app for Prerender.io support, countless optimizations and fixes, simpler integrations, and more.
Earlier this year, we welcomed Mehdi Karimi, Ph.D. as our new director of cybersecurity to lead us in maintaining the highest levels of security in the industry. dotCMS (re)achieved SOC2 Type 2 certification with no exceptions for 2022. Most recently, we received authorization as a CVE Numbering Authority. In addition, we have a strong security roadmap in place for this year, including data privacy GDPR/CCPA certification, ISO 27001 certification, and setting up a formal vulnerability/bug bounty program that would allow us to publish and engage with security researchers. Moreover, we recently incorporated SonarQube into our workflow, making regular static code-security analysis an ongoing part of our development process.
We follow a tried and true methodology for our roadmap.
You can view the complete roadmap here. We also welcome ideas and advocates, and public feedback via email: email@example.com.
The latest version of dotCMS features updates to the Block Editor, new templating tools, and other content-related improvements.
We first rolled out the Block Editor in version 22.05, and it’s improved steadily since, quickly becoming one of the most important pieces in our content arsenal. The Block Editor offers rich editing for both headless and traditional implementations, the ability to embed and render user-created content in a variety of ways, simple image handling, and more.
Here’s what we’ve added to it in version 23.01 alone:
When making edits using the Block Editor, content is stored as JSON objects under the hood. That JSON is then parsed and dropped into a component, and that component can deliver content in any way you see fit.
In the near future, we plan to introduce:
Marketing teams accustomed to platforms like WordPress will be able to discover pages more easily and quickly edit, copy and generally streamline how they work within dotCMS.
Modeled after best-of-breed systems, experiments and A/B testing will allow dotCMS users to add experiments to different pages to create and monitor variants without interrupting your flow.
An integration of integrations, this allows you to push content to Zapier as content moves through a workflow process. For example, push to Slack, Google Drive, or any 3rd party system. dotCMS users will also be able to Ingest content from Zapier, for example, add/edit content objects using Google sheets.
Version 2.0 of our CLI will be moved out of bash and into Quarkus. This microframework allows developers to write Java that can be compiled down to binaries that are executable on all platforms. Part of this process will include redefining some of our APIs.
Some of the other features that we hope to implement in the future are:
See a demo of some of these latest updates in our Fall Update Webinar: dotCMS Fall 2022 Product Update.
Maintaining or achieving a global presence requires effective use of resources, time and money. Single-tenant CMS solutions were once the go-to choices for enterprises to reach out to different market...
What is cloud computing, and what benefits does the cloud bring to brands who are entering into the IoT era?
What’s the difference between a headless CMS and a hybrid CMS, and which one is best suited for an enterprise?