ContentSync Logo

Roadmap

2025

Q4: Official release

Following our current beta testing phase, Content Cloud will be released as stable on November 15, 2025.

Q4: Onboarding

The documentation and the onboarding experience will be improved to showcase more real-world use cases and provide simpler getting-started guides for new developers.

Q4: prosemirror Drupal module

prosemirror will be the first non-HTML rich text module for Drupal that’s dedicated to supporting scalable omnichannel publishing in Drupal. The module will be fully open source and not require a Content Sync subscription. It’s capable of rendering HTML when used inside of Drupal but can provide structured JSON data through Drupal’s REST APIs to make it easy for consumers to render content outside of Drupal.

Having a true omnichannel rich text format is critical to, e.g., provide custom link rendering and navigation in apps, for rendering media in an optimized way and for having the necessary control of the display.

Example: The documentation you’re looking at right now uses the rich text format from prosemirror for rendering content inside a custom Next.js app; the navigation on the right is generated based on the headline tags in the document. Links to other content use the Drupal path alias (slug in Content Cloud) but they don’t link to the Drupal source site, giving us full control over the navigation, rendering, and user experience.

2026

Q1: Syncing back to Drupal

We are adding an option to synchronize changes you make in the Content Cloud back to Drupal. This allows users to create their own content entry and management UIs in, e.g., React that will update content and translations in all connected Drupal sites.

This will come with its own fully typed client code for managing content as seamlessly as you can deliver it today.

2026 and beyond

While there are many more features, extensions, and improvements to come, we have not prioritized them yet. Please reach out to us if you’re interested in other features or if you are curious about what’s next. We’d love to hear from you! This is an unofficial list of ideas we’re prototyping (no specific order):

  • Provide the uuid, customId, name, and slug properties in all entry link properties to simplify and optimize content navigation in frontends.

  • Provide custom external link properties to simplify frontend routing.

  • Optimize content structure for various Drupal providers like Layout Builder. See here for a full list.

  • More standard source integrations, e.g., for Contentful and Wordpress.

  • Support for webhooks.

  • Support for Automatic Persisted Queries (APQs) in GraphQL.

  • Support for self-service custom integrations with ERPs, CRMs, PIMs, Analytics, Recommendation engines, etc.