[DRAFT] Common components
Content Management Systems (CMS)
- Last reviewed
- 7 September 2026
- Owner
- Head of Architecture
Notifications and messaging
Notification components will enable your service to deliver messages to users. We have two main categories of notification applications - ‘communication’ and ‘error tracking’.
Communication
These applications will let your service send out email, SMS (text messages), letters, or a combination of all three, using HTTPS or SMTP protocols:
GovUKNotify SMTP Sparkpost Intellisoft SMS Send Grid Error tracking
These applications will provide error monitoring and alerts to services that are developing solutions, so that they are aware of errors as they appear:
Rollbar Sentry Each application brings a slightly different set of features and capabilities that fit different use cases. This table provides an overview:
Image of the DfE Notification Capabilities
Here’s a link to an Excel version of the table.
If you’re considering your options and want more advice, get in touch with your Architecture Lead.
Content Management Systems
A Content Management System (CMS) allows users to create, manage, modify, publish and store digital content in one place.
‘Headless’ content management is being used increasingly within services in the department. This is a back-end only CMS that makes content accessible via a RESTful API, for display through one or more front-end channels.
CMS products support collaboration across teams, with multiple users being able to work on content in the back-end of the CMS, allowing for quick and easy updates. CMS users can customise the design and functionality of the front-end by using templates and extensions.
Contentful is the department’s preferred headless CMS product, which is currently in use by a number of services. Contentful has an enterprise license plan and support, and has been assured for use in DfE, meaning teams can purchase the space size they need and incorporate into their service easily. For more information, contact the digital tools support team via their Digital Tools SharePoint site.
Other CMS products either in use or have been considered across the department are:
Orchard Core Sitefinity Contentstack Kontent Prismic Cosmic JS Benefits of using a CMS include:
No coding knowledge required - Enables non-developers and other users to build websites without coding. (It’s important to note that most CMS applications do allow users to add custom code for more granular control.)
Easy collaboration - Multiple users can access and work in the back end of a CMS at the same time.
Features, extensions and templates - CMS applications offer built-in features as well as add-ons to customise digital content.
Easier updates - Enables users to make changes to digital content faster and easier, to keep content dynamic and relevant.
Each CMS brings a slightly different set of features and capabilities that fit different use cases. This table provides an overview:
Image of the DfE Content Management System Capabilities
Here’s a link to an Excel version of the table.
If you’re considering CMS options, please discuss your needs with DfE Content Design community on Slack. Work on the strategy for information services within the DfE is ongoing.