This roadmap outlines the current and planned evolution of the Forrit CMS platform. It provides visibility into the capabilities available today and the strategic investments being made to support better content experiences, increased operational efficiency, stronger governance, and the adoption of AI-powered digital services.
Q3/4 2026 Priorities
-
AI-Powered Content Services - Provide a secure and governed way for AI assistants and agents to find, understand and work with content held within the CMS. Vector-based search will help users discover relevant information using natural language, while reusable CMS skills will allow authorised AI tools to carry out specific content tasks and support automated workflows. Authentication, traceability and auditing will ensure organisations retain visibility and control over access, information used and actions performed.
-
Template Management - Create a complete templates capability that allows organisations to define, manage and reuse page structures and content patterns across websites and digital services. This will improve consistency, accelerate content creation, and reduce duplication of effort when building new sections or sites - template support already available in v5 and this expands functionality to the UI
-
Enhanced Metadata Management - Improve the management of metadata for pages and media assets, providing a more structured and user-friendly way to capture information that supports searchability, governance, reporting, accessibility, SEO and future AI-driven content experiences
-
Link Field Type - Introduce a dedicated link field type that allows internal and external links to be managed consistently throughout the CMS. This will improve content quality, simplify authoring, and provide a stronger foundation for navigation, cross-linking and future automation
-
Task Rollback - Provide the ability to reverse workflow actions and content tasks where appropriate, allowing users to recover from mistakes quickly and confidently. This will reduce operational risk and improve trust in publishing and approval processes
-
Branching and Merge Capabilities - Extend content management capabilities to support the creation, editing and merging of content changes outside the primary publishing workflow. This will allow teams to work on larger content changes, campaigns or restructures in isolation before incorporating them into the live environment
-
Platform and User Experience Updates (Angular/Material core) - Upgrade core user interface frameworks and supporting components to ensure the CMS remains secure, accessible and aligned with modern user experience standards. This work will improve maintainability, supportability and the overall experience for content authors and administrators.
From Q1 - 2027
-
Simplified Content Editing – Customisable content editing views - Provide a way of navigating too and grouping content entries that make logical sense to the users who need to locate and make changes. If this cannot be done based on existing page data, then look at adding extra layout instructions for templated pages that defines a content editing experience.
-
Multi-Cloud Capability - Get the solution running on a different cloud to work out what the minimum set of services would be to support the CMS. This could be AWS/Google or a sovereign cloud provider like OVH Sovereign cloud
-
Autonomous Agents - Create a framework for defining and launching agents to do specific jobs based on triggers from the CMS. How these agents interact with the CMS and provide feedback to the CMS users.
-
Intelligent Media Service - Create an optional Intelligent Media Service that has a configurable set of outputs based on an initial media upload.
-
Forms Service - Create the capability in the CMS to define forms, add intelligence in the SDK to process forms in the consumer app/experience layer. Define a forms service that will store responses until pushed to the ultimate destination. The CMS would not be involved in the forms processing just the form definition. The ideal would be the forms service is just a transient processor and would delete any data once processed to reduce any PII exposure
-
Advanced Workflow Capabilities - Suggestion would be to choose an enterprise workflow framework like Power Automate and demonstrate the CMS as an initiator and consumer of actions/steps with full visibility appearing in tools like Teams and Outlook on the progress of workflows
-
Seamless SEO, AEO, GEO and Accessibility - Provide an opinionated process for site structure and the capture of required meta-data to fully support GEO and WCAG. As part of the publish process annotate existing assets and produce the specific assets required as a base for full SEO, GEO and WCAG support
-
Complex Content Organisation – Namespaces - This would introduce scoping of content to allow the equivalent of RBAC over content. Allowing different people/groups to manage different aspects of a site. It would also support multiple small sites that were all based on a shared structure
Note: This roadmap outlines the planned evolution of the Forrit CMS platform and should be viewed as an indication of our current direction rather than a fixed delivery plan. Our product steering committee reviews priorities on a regular basis, ensuring investment remains aligned with customer needs, technological advances and strategic objectives. Consequently, features, priorities and timelines may change over time.