Stefan Schinkel
Chief Revenue Officer

The Primer For Your Digital Experience Platform - dotCMS APPS

Nov 16, 2020
By: Stefan Schinkel

Building a digital experience platform is all about interoperability with adjacent applications in the digital marketing stack. The minimum viable marketing stack for any enterprise-grade digital experience platform, next to the CMS, consists of a marketing platform (MA, CRM), Digital Asset Management, and Analytics. In a commerce play (DTC, B2B, B2C), you would also include an e-commerce platform. Having REST and GraphQL APIs makes the integration play already much easier, and the scriptable API builder accelerates any integration between dotCMS and API-based platforms and applications. Let’s not forget the power of webhooks and the key role they can play in your dotCMS-based digital experience platform.

Digital Experience Platform (DXP)

How Apps is helping IT teams

Having all integrations with dotCMS in a centralized place drives the total cost of ownership and return on investment from a maintenance & support perspective. dotCMS Apps provides a secure store for plugin and system configuration and gives dotCMS users the ability to surface and configure custom dotCMS functionality. dotCMS Apps can be combined with OSGI plugins and custom REST endpoints to provide custom functionality that supports your critical use-cases.

How Apps is helping business teams

With dotCMS Apps, it is possible to provide more control over the integration or custom functionality to non-technical CMS users versus hard-coded integrations that would require a developer to make changes. dotCMS Apps provides the framework to make this happen. It helps teams find the right balance between business agility and IT dependency as they build out their digital experience platform and drive their digital ambitions.

How Apps helps Digital Agencies

The current iteration of dotCMS Apps is just the beginning of what can be an actual marketplace of value, adding Apps for dotCMS-enabled digital experience platforms. The ambition is to have an App exchange like Salesforce eventually. We’re not there yet, but starting today, digital agencies can create their own intellectual property and expose it as Apps in their dotCMS implementation.

Native Apps

dotCMS released dotCMS Apps with four native Apps. These Apps will be maintained and supported going forward by the dotCMS product team as parts of your dotCMS Enterprise or dotCMS Cloud subscription:

Amazon Rekognition - the AI-driven solution that is widely used to automatically tag all your images and videos will help drive your content search & findability.

Edit Mode Anywhere - the cutting-edge Single Page App (SPA) editor that drives editor experience and agility when running dotCMS as a headless or hybrid CMS. More details and action.

Google Translate - Translate your engaging content with Google Translate to the language of your key markets. Drop your Google Translate API keys in and start translating your digital experiences for the rest of the world.

SAML-based SSO - including access to dotCMS via your enterprise-wide Single Sign-On solution, based on SAML, whether it is Azure AD, Google, Okta, or any other Identity Provider (IdP).

Example of an Apps-enabled Plugin

You can find a simple example of a dotCMS App at

What’s next for dotCMS Apps?

dotCMS plans to release more native Apps as we go forward and expect to see Apps for Marketing Automation, Digital Asset Management, Customer Relationship Management, e-Commerce, and many more.

Filed Under:

Recommended Reading

Why Global Brands Need a Multi-tenant CMS

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...

14 Benefits of Cloud Computing and Terminology Glossary to Get You Started

What is cloud computing, and what benefits does the cloud bring to brands who are entering into the IoT era?

Headless CMS vs Hybrid CMS: How dotCMS Goes Beyond Headless

What’s the difference between a headless CMS and a hybrid CMS, and which one is best suited for an enterprise?