Disclaimer: The roadmap contained herein consists of good-faith release estimates on a quarterly basis. However, none of the dates should be considered hard commitments.
To watch the full dotCMS 2025 Roadmap presentation from Director of Product Freddy Montez, please visit our YouTube.
Product Themes for 2025
In 2025 we continue to focus on making dotCMS a product for both Developers and Content Teams, leaving no one behind as we expand and deepen its capabilities. We concentrated our development into four main themes for 2025:
Making it easy for developers to build engaging experiences on any technology
Delivering AI driven content creation and management capabilities
Expanding our content optimization features of Personalization, Analytics, and A/B Testing
Evolving our deployment architecture to deliver zero downtime, zero testing upgrades while maintaining rock solid security and compliance standards
Build Engaging Experiences
One of the main issues with headless CMS' is with previewing content and managing content in context for those experiences. dotCMS makes it easy for developers to render their headless applications inside dotCMS so content teams can easily make content and layout edits in context, preview content as it will appear in the app, and access tools like Future Time Machine and A/B testing all in a consistent user interface no matter what technology the front end application is built in.
PHP & JavaScript SDKs help developers get up and running easily, facilitating integration with dotCMS, rendering in UVE and enabling tools like A/B testing, Analytics, and Time Machine for their headless apps.
UVE Future Time Machine lets content teams preview scheduled content as it will appear on the page at any future date, eliminating uncertainty by viewing scheduled content changes in context.
UVE Content Palette makes using the Content Type tool in our Universal Visual Editor much easier, getting you to the content types you need faster and making page building easier.
UVE Style Editor frees up developer time by giving content editors more control over what the content looks like on the page through configurable controls within content components.
dotAI in JavaScript SDK makes it easier for front end developers to integrate dotAI features for their front ends, accelerating AI-powered content experiences while maintaining the same developer experience standards as existing dotCMS SDKs.
AI Driven Content Creation & Management
dotCMS already has robust content management features, in 2025 we are supercharging these by redesigning the user experience and more seamlessly integrating AI to help create, edit, and manage content through the system.
Edit Content Screen: We’re redesigning our edit content screen to improve the usability, add capabilities, and make tools and Workflow actions easier to access and use.
Block Editor Upgrade updates the block editor field type to use the latest stable version of Tiptap, allow cut and paste from markdown, ingest images that are dropped in, and move to official Tiptap extensions for things like drag and drop and bubble menus.
dotCMS Redesign will greatly improve the usability of our back end application, making it more intuitive and consistent, helping content teams get content to market faster. We are starting on the full redesign by updating the breadcrumb menu.
Content Drive streamlines managing and searching content, files, and site folders in the back end, making it easier to find content and files, move and copy them between sites and direct users to the folders and files they need.
dotAI MCP Server is our initial implementation of MCP infrastructure. Our MCP has the capability to learn about your dotCMS instance, answer questions about the content and content structures, create content, send it through workflow and even create content types. Our MCP is also integrated with Cursor and can be used to create front end components based on content structures as well as from Figma designs. This area is evolving quickly so expect more capabilities here soon!
Angular Version Update is an internal update to the back end that brings our UX up to date with the latest Angular version.
Content Optimization
Helping content teams plan what content to focus on by understanding what content and experiences are working, as well as optimize the delivery of content through testing and personalization is a main focus for 2025. Getting content to market quickly is just one piece of the puzzle, making sure it is the right content for the right person at the right time is critical for content ROI.
Content Analytics Dashboard MVP introduces pre-built reports for content analytics accessible from the back end of dotCMS. This is being used internally at dotCMS and will be available to customers soon!
Content Analytics Conversions & Attribution expands the data collected by analytics to show what content in your system is leading to conversions. This will serve as a foundation to drive AI powered insights and actions with A/B testing and Personalization, creating a powerful optimization engine in 2026!
dotAI Additional Vendors opens up our dotAI offering to virtually all LLM models, even custom or private models. Today dotAI is driven by OpenAI integration exclusively, in the near future customers will be able to integrate LLMs of their choosing and designate specific LLMs for specific jobs within dotCMS.
Flexible Deployment
Import REST API makes large scale content migrations between environments and from other platforms easier to manage and faster.
In Place Upgrades is a set of several improvements to our upgrade processes and infrastructure that will allow dotCMS to deploy more often, with less risk, and with zero downtime. It will also improve the migration experience for customers moving from one LTS to another as well as give customers on Evergreen more flexibility when consuming constant upgrades.
SOC2 for GCP keeps dotCMS compliant as we expand our infrastructure to hold more sensitive types of customer data on Google Cloud Platform
OpenSearch Compatibility will include dotCMS conducting compatibility testing for newer versions of OpenSearch such as 2.19 and 3.0, identifying any breaking changes or required code modifications, and documenting upgrade paths for customers.