Changelog

The Optimization SDK has been enhanced to fully support mobile SDKs, bringing personalization and analytics to native mobile platforms.

The release includes:

• @contentful/optimization-react-native — React Native SDK with offline-aware event handling, screen tracking, and in-app preview panel.
• Swift SDK — Native iOS SDK for personalization, screen tracking, and consent management.
• Kotlin SDK — Native Android SDK for variant resolution, screen tracking, and consent management.

With this improvement, you can now use the Optimization SDKs to deliver and measure personalized experiences across web, server, iOS, Android, and React Native using a consistent approach.

The SDKs help you:

• Bring personalization and analytics to your native mobile experiences.
• Use familiar patterns and APIs across web, server, and mobile.
• Track screens and measure engagement within your mobile apps.
• Manage user consent as part of your integration.
• Deliver consistent personalized experiences across multiple channels.

You can install the mobile SDKs using npm for React Native, Swift Package Manager for iOS, or Maven/Gradle for Android. For more information on how to get started, see the Optimization SDK documentation and GitHub repository.

You can now pull Contentful content directly into Figma with the Contentful for Figma widget, making it easier to create and test designs with real content, without having to manually copy, and paste content into Figma.

The widget connects structured content from Contentful to components and full-page designs in Figma, helping teams test realistic variations earlier in the creative process, and create a clearer handoff to development.

With the widget, you can:

• Map Contentful content types to Figma frames.
• Populate designs with existing Contentful entries.
• Try different content variations within the same layout.
• Refresh designs with the latest content updates.

Install the widget from the Figma community, connect it to your Contentful space, and get started. Use the widget to preview content variations across components or populate complete page designs with assembled content.

For more information about setup and requirements, see Contentful for Figma and the Concepts page for more context.

Automations is now releasing usability improvements to the visual builder and more, making it faster to build and easier to spot and fix issues as you go.

• Auto-save on nodes: Changes to a node are saved automatically as you configure it, so you only need to click Save once for the full automation.
• Visual validation errors: Misconfigured nodes are flagged in real time with a red indicator on the canvas and sidebar, so you know exactly what to fix.
• Guided and filtered field selectors: Dropdowns now use a two-stage category-then-value flow, and field pickers automatically narrow to the relevant content type's fields.
• Drag-to-reorder: You can drag any step to a new position directly in the canvas instead of deleting and re-adding it.

We've also added the ability to copy a step's ID directly from its node for use in advanced configurations, and AI Action nodes can now optionally validate their output against a target field before passing it downstream, helping catch mismatches early and avoid failures further along in the automation.

For more information, read Work with automations and Automations: use cases.

You can now easily configure and verify your Contentful Personalization setup using the step-by-step guide provided on the “Setup and health” tab in the Contentful Personalization app configuration page.

The guided experience offers better visibility into the required steps for a correct setup, and provides teams a reliable way to monitor whether their implementation stays healthy over time.

Once you’ve completed all the steps, the “Setup and health” tab displays an overview of key information to manage your setup, such as SDK version, event streaming health, and data freshness.

For more information about the steps, see the Setup and health page.

The Content Exporter app helps teams export entries from Contentful in bulk, while using filters, field selection, and multiple file formats to generate the dataset they need.

The app helps content teams, developers, and operations teams work with large entry sets more easily, without relying on the Contentful web app's 40-entry export limit, manual export workarounds, or one-size-fits-all files. Teams can narrow results before export, preview matching entries, and choose the fields and format that fit their migration, analysis, or archiving workflow.

Key features include:

• Bulk entry export: Export entire content types or search across all content types without the 40-entry export limit in the Contentful web app.
• Filter and preview: Narrow results by status, tag, taxonomy, date range, locale, or field value, then review matching entries before downloading.
• Flexible field selection: Select the specific entry fields to include so each export contains only the content your team needs.
• Multiple file formats: Download exports in CSV, JSON, XLSX, XML, or YAML for migration, analysis, or archiving.

Get started by installing the Content Exporter app from our Marketplace.

We have upgraded the usage reporting experience in the Contentful web app and released a new public Usage API. These updates provide comprehensive visibility into your consumption patterns, allowing you to track trends, identify anomalies, and make data-informed decisions about your resources.

Web app usage reporting updates

These improvements apply across the Asset Bandwidth, API Calls, Functions, and AI Actions dashboards:

• Custom date selector: You can now select any custom date range of up to 31 days, going back 12 months, to analyze specific periods of activity.
• Daily usage charts: A new daily chart displays absolute usage totals for your selected 31 day window, making it easier to pinpoint exact days with traffic spikes.
• 12 month trend charts: A new macro level chart displays usage aggregated by calendar month, helping you understand long term seasonal trends and plan capacity.
• Uncapped space breakdowns: The API Calls dashboard no longer limits the space breakdown to the top five spaces. You can view all active spaces and sort them by specific API types (CDA, CMA, CPA, or GraphQL).

New usage API and endpoint deprecation

Developers can now programmatically access the exact same granular usage data that powers the web app dashboards.

New endpoints: Use the /metric endpoint to pull time series data for any usage metric, and the /usages-detailed endpoint to pull granular, per asset bandwidth breakdowns. The Content Management API (CMA) JavaScript SDK has been updated to support these endpoints.

Endpoint deprecation: The release of the new Usage API marks the official deprecation of the legacy /organization_periodic_usages and /space_periodic_usages endpoints. Developers must migrate existing scripts to the new endpoints. Please review the breaking change and follow our migration guide to update your scripts to the new endpoints before February 28, 2027.

Learn more

Usage API reference

Asset bandwidth usage reporting documentation

Usage API migration guide

Breaking API changes details

Starting August 18, 2026, Enterprise customers can stream audit log events to their cloud storage destination within approximately 5 minutes of the event occurring.

Near real-time audit logs give security and platform teams immediate visibility into who is accessing and changing content across their organisation. Events arrive in minutes, enabling fast detection and investigation of suspicious activity, and feed directly into existing security workflows and SIEM tools. Events are delivered in OCSF format (Open Cybersecurity Schema Framework), compatible with major SIEM tools including Splunk, Datadog, and Azure Sentinel.

With near real-time audit logs, you can:

• Receive audit events within approximately 5 minutes to your AWS S3, Azure Blob, or Google Cloud Storage destination.
• Monitor who accessed or changed content in near real time and feed events directly into your existing security workflows.
• Capture read access (GET requests) in addition to write operations, giving you visibility into who viewed sensitive content.

Near real-time audit logs and daily audit logs operate independently and continue to co-exist.

Near real-time audit logs are configured through the Enterprise Observability UI, under Organization settings > Observability. Or by using the Management API (CMA).

To learn more, see the near real-time audit logs documentation.

Contentful has added email and webhook notifications for scheduled Timeline release outcomes. Release creators and last editors receive emails when a scheduled release fails or completes successfully, helping teams spot release outcomes without adding new failed-release workflows in the Timeline interface.

This update helps teams respond faster when a scheduled release fails, confirm successful scheduled releases, and route release outcome signals into shared operational channels or external systems.

Use email notifications and webhooks to monitor scheduled release outcomes:

• Release completion emails - Contentful automatically sends an email to the release creator and last editor when a scheduled release fails or completes successfully.
• Webhook monitoring - Subscribe to the ReleaseAction topic with the execute event to receive a webhook when a release publish succeeds or fails.
• Release status - Use sys.status in the webhook payload to identify the outcome. A succeeded status means the release was published successfully, and a failed status means the release publish failed.
• Publish filtering - To monitor publish outcomes only, check that action === "publish" and inspect sys.status for succeeded or failed.

Implementation notes:

• Email recipients are limited to the release creator and last editor and cannot be configured by users.
• Success emails do not include a link back to the successful release.
• Webhook payloads can be used for monitoring and automation, but failure details may be limited.

For more information, refer to the Timeline releases.

The Audit Log Viewer app helps Contentful administrators view organization-wide audit activity directly inside Contentful, while reading audit log files from a configured cloud storage bucket.

The app helps admins, security teams, and operations teams investigate changes more easily, without piecing together activity across individual spaces, searching raw log files, or exposing storage credentials in the browser. Teams can load a specific date range, filter audit events, and review activity across every space from a single view.

Key features include:

• Organization-wide audit visibility: View audit activity across every space in your Contentful organization from one centralized interface.
• Search and filtering: Filter audit events by space, actor, action type, or free text across entity IDs and API paths.
• Summary charts: Review events over time, top actors, and action breakdowns to understand activity patterns faster.
• Secure storage access: Keep storage credentials server-side in a Contentful Function while the browser receives short-lived, read-only pre-signed URLs.
• Flexible activity review: Load historical activity by date range, browse paginated results, and scan key actions with color-coded badges.
• Configuration recovery: Preserve non-secret settings locally so they can be restored if a bundle update resets the app.

Get started by installing the Audit Log Viewer app from our Marketplace.

The Adobe Experience Manager Asset Selector app helps teams browse, search, and select approved AEM Assets directly inside Contentful, while keeping asset access aligned with Adobe IMS permissions.

The app helps editors, marketers, and creative teams attach DAM assets to Contentful entries more easily, without leaving Contentful to search AEM, downloading and re-uploading media, or relying on asset path lookups. Teams can use Adobe's Content Advisor picker inside an entry field, manage selected assets after adding them, and apply governance controls for approved asset selection.

Key features include:

• In-entry asset discovery: Find approved AEM assets from a Contentful entry field using Adobe's picker, reducing tool switching during content production.
• Edit asset selections: Arrange selected assets or remove them from the field after selection, so entries stay easy to review and maintain.
• Adobe permission alignment: Authenticate through Adobe IMS OAuth so editors work with the same asset access permissions configured in AEM.
• Repository and upload controls: Limit browsing to the right AEM repository, tier, or environment, and hide uploads when editors should choose from approved assets only.

Get started by installing the Adobe Experience Manager Asset Selector app from our Marketplace.

To learn how to configure and use the app, refer to Adobe Experience Manager Asset Selector article.

The Optimization Agent is now available in Contentful Personalization. It helps marketers, editors, and analysts move from questions to answers by providing contextual, AI-powered responses about their content and performance as text and visual elements.

You can use the Optimization Agent to:

• Ask natural-language questions about your content and performance data.
• Explore insights without manually building reports or searching across multiple views.
• Ask follow-up questions to refine an answer or explore a topic in more detail.
• Surface potential opportunities for content and experience optimization.

The Optimization Agent brings intelligence closer to the decisions teams make every day, helping them move from understanding performance to deciding what to optimize next. It is part of Contentful’s broader optimization experience, which connects content, audiences, and performance outcomes in one workflow.

For more information, see the Optimization Agent page.

Contentful Personalization now contains the following analytics capabilities to help you understand not only what you published, but how that content is actually performing:

• Content insights: Analyze your content performance, both at an entry-level and at a content type- level, and check out the content effectiveness uplift for your configured metrics.
• Audience insights: Look at your audience impact, identify which audiences are driving results, and understand who they reach.
• Benchmarks: Compare your entries, groups of entries, or audiences, and make decisions based on performance rather than assumptions.

With these capabilities, you can better understand how your content is performing directly in the workspace where you create and personalize that content.

This improvement brings content creation and measurement together in one space. Marketing, content, growth, and experimentation teams can move from “we published something” to understanding which content and audiences are contributing to outcomes, without stitching together multiple analytics tools or relying on a data team.

For more information, see Content Insights, Audience Insights, and Benchmarks.

You can now filter taxonomy concepts by ID with the Content Delivery API using the sys.id[in] query parameter, matching the filter already available on the Content Management API. Use it to fetch a known set of concepts in a single request instead of paging through the full collection.

For more information, see the Taxonomy CDA Documentation.

As an administrator in our Enterprise plan, you can now set up to five independent SSO configurations in one Contentful organization, each with its own identity provider. Support users across business units, regions, and subsidiaries without splitting into separate organizations or exempting anyone from SSO. Users simply enter their email address to sign in and are routed to the right identity provider automatically.

Add a configuration under Access Tools > Single Sign-On (SSO). See our SSO support page to learn more.

We have released the Optimization SDK, a new developer toolkit for integrating Contentful Personalization and Analytics across web and server applications from a single foundation.

The Optimization SDK includes:

• @contentful/optimization-web: Browser SDK for personalization, analytics, and consent management.
• @contentful/optimization-node: Server SDK for server-side rendering (SSR).
• @contentful/optimization-react-web: React integration with providers, hooks, and router adapters.
• @contentful/optimization-nextjs: Next.js integration for SSR, hybrid rendering, and client-side tracking.
• @contentful/optimization-core: Core SDK.

The Optimization SDK simplifies implementation and helps you get up and running faster. It provides:

• A unified SDK experience across web and server applications.
• Built-in support for server-side rendering, including Next.js.
• Less implementation code and faster setup.
• Built-in consent management, automatic interaction tracking, and preview support.

We recommend using the Optimization SDK for all new Personalization and Analytics integrations. Existing integrations built with experience.js continue to be supported.

For more information, see the Optimization SDK developer documentation and the open-source Github repository.

• The Contentful Remote MCP server has been moved out of Beta and into general availability.
• The authorization flow for the Remote MCP Server has been slightly changed. Going forward, users must add the MCP Config App to Space Environment pairs that they want to use the MCP server with.
• The MCP server is available to all customers without charge.
• You can find the Contentful Remote MCP app in the Contentful App Marketplace.

Starting July 21, 2026, Enterprise Observability now streams GraphQL API logs to your cloud storage, extending near-real-time log delivery to your GraphQL API traffic.

GraphQL logs are delivered as structured JSON files to your configured AWS S3, Google Cloud Storage, or Azure Blob Storage destination, using the same near-real-time, ~5-minute batching model as Delivery API (CDA) logs. From there, you can ingest them into your existing observability tools (Datadog, Splunk, Grafana, or similar) to debug query errors, monitor latency and response behavior, and correlate GraphQL activity with traffic from other Contentful APIs.

To configure GraphQL log delivery, navigate to Enterprise Observability in your Organisation settings, select GraphQL as a log type, and map it to a destination.

To learn more, see the Enterprise Observability documentation.

Organization admins can now filter CMA tokens by author and configure a maximum expiration limit for PATs, from a cleaner Token Management settings experience.

This makes it easier to review user-owned tokens during offboarding, security checks, and governance reviews, while also giving admins a more consistent way to enforce token lifetime expectations for personal access tokens.

The maximum token expiration policy applies to newly created PATs and does not retroactively change existing ones.

This update is available to all customers.

You can now see audience size estimations while building an audience in Contentful Personalization, making it easier to understand its potential reach before using it in campaigns, personalizations, or experiments.

As you configure your audience, preview metrics are displayed directly in the Rule builder on the Editor tab. These estimates update automatically whenever you modify your audience rules, including changes to traits, filters, or locations.

The available preview metrics include:

• Profiles in audience: An estimate of how many profiles match your audience definition.
• Estimated views: An estimate of the number of views your audience is expected to generate.
• Estimated conversion rate: An estimate of the audience's expected conversion rate.

For more information, see the help center documentation.

We have just released Bulk entry content operations that provide developers and platform teams an efficient way to manage multiple entries simultaneously, reducing the number of API calls required for bulk content management.

You can now perform the following entry operations in bulk through the Content Management API:

• Create, update, delete, and export, with a limit of 10,000 entries per job

Each job processes the entries asynchronously, returns per-entry results so teams can retry only what failed, and surfaces job status that teams can poll or receive via Webhook notifications. There are no custom monitoring layers needed.

For more information, see the Bulk entry operations and the Content Management API page.

Starting May 28, 2026, Enterprise Observability log streaming can now deliver Content Delivery API (CDA) logs to Microsoft Azure Blob Storage, alongside existing support for Amazon S3 and Google Cloud Storage. This enables teams running on Microsoft Azure to route Contentful API activity logs directly into their existing observability stack, with no need to route through a third-party destination.

For details, see the Enterprise Observability: Microsoft Azure Blob Storage setup

The Drive Integration app helps teams keep authoring and collaborating on the content changes in Google Docs, and then import finalized documents into Contentful as structured draft entries. It reduces manual copy-paste work by using AI-assisted field mapping, supported formatting, and image handling to move approved content into an existing Contentful content model.

The app helps content teams, editors, and admins manage long-form content more easily, without the need to manually copy-paste, format, and clean up content. Teams can select Google Docs they would like to import into Contentful, review suggested field mappings before import, skip content that should not be included, and continue publishing through their standard Contentful workflow.

Key features include:

• Google Docs Import: Browse Google Drive, select a desired Google Doc, and import it into Contentful as a draft entry.
• AI-Assisted Field Mapping: Review and adjust mapping suggestions so document sections can be placed into the right fields matching your existing Contentful content model.
• Supported Formatting And Images: Preserve common document structure, including headings, text formatting, lists, hyperlinks, embedded images, and tables where supported by the target field.
• Permission-Aware Drive Access: Each user connects their own Google account, and the app displays only Google Docs and folders they already have permission to access in Google Drive.

For more information, see Drive Integration app documentation.

We have created and released Contentful Skills, an open-source collection of agent skills designed to integrate Contentful guidance directly into your AI coding agent of choice, with an emphasis on Contentful Personalization.

These skills can teach your coding agent how to build on Contentful. Once installed, your agent starts providing context and codebase-aware guidance about SDK setup, Draft Mode, content migrations, and personalization directly within the workflow you already use.

The collection contains the following skills:

• contentful-guide – Explains the core concepts and routing. This is the entry point that helps the agent decide which skill to use for which question.
• contentful-api – Language-agnostic REST and GraphQL API reference - cURL examples for CMA, CDA, CPA, Images, and GraphQL.
• contentful-nextjs – SDK setup, content fetching, and Draft Mode previews for both App Router and Pages Router.
• contentful-migration – Writes and runs content model migration scripts.
• contentful-personalization – The flagship. Four interactive workflows in one skill: Onboard, Live debug, Doctor, and Develop.

For more information, see our blog post.

To accommodate our customers' needs, we have increased the maximum number of template versions per content model template from 200 to 1000.

For more information about content model templates and template versions, see the Help Center documentation.

Starting May 19, 2026, Enterprise teams can now manage key space setup steps through the Content Management API. With this release, you can list available licenses for an organization, check eligible licenses for a space, create a paid space with a selected license, unarchive a space with a selected license, and view or manage space add-ons for environments, content types, and records.

This removes a key manual step from multi-space provisioning and makes space setup easier to automate at scale.

This release is intended for developers and platform teams with org owner or admin permissions who manage many spaces through automation or internal tooling. It does not cover trial-space management or upgrade and downgrade flows in this release.

For more information, see: Create a space, Unarchive a space, Eligible licenses, Available licenses, Get space add-ons from a space and Allocate or deallocate space add-ons.

Starting May 19, 2026, Enterprise Observability log streaming can now deliver Content Delivery API (CDA) logs to Google Cloud Storage, alongside existing support for AWS S3. This enables teams running on Google Cloud to route Contentful API activity logs directly into their existing observability stack, with no need to route through a third-party destination.

For details, see the Enterprise Observability: Google Cloud Storage setup.

Starting May 19, 2026, AI Actions now supports Azure OpenAI as an additional bring your own model (BYOM) connector.

This allows organizations using Microsoft Azure to connect Azure-hosted OpenAI models directly into Contentful AI Actions. Azure OpenAI joins the existing supported AI provider connectors, including OpenAI, AWS Bedrock, Google Gemini, Google Vertex AI and custom model connectors.

Once configured, Azure models can be used in AI Actions for generation and validation workflows.

Learn more in our Azure connector setup guide.

Starting May 19, 2026, AI Actions now support assignment and filtering configurations to help teams control where AI Actions appear and how they run. You can assign actions to specific content types and fields, configure default variable values, and reduce repetitive tasks for editors.

This release applies to AI Actions in Contentful. Existing AI Actions, content models, and editor workflows remain unchanged.

With these new assignment and filtering configurations enhancement, you can:

• Show AI Actions only where they are relevant by assigning them to specific content types and fields.
• Improve localization workflows by limiting translation actions to specific fields, such as translating only body content instead of entire entries, and pre-configuring which languages are available for translation.
• Support brand consistency by applying brand-checking actions only to fields like titles and content where messaging matters most.
• Reduce editor friction by preconfiguring and locking variable values such as locales or brand guidelines rules.

Learn more in our Help Center.

The Google Analytics 4 app now helps editors view page performance metrics directly inside the Contentful entry sidebar, while keeping analytics connected to the right entry even when pages use complex URL structures or multiple URLs.

These updates help content teams understand how each entry is performing without leaving Contentful or manually checking Google Analytics 4. Teams can map entries using standard slug and prefix settings, and configure advanced URL patterns for localized segments, query strings, wildcard segments, and multiple rules per content type.

Key features include:

• Entry Performance Insights: View total or unique page views, trends over time, and deep links into Google Analytics 4 directly from the entry sidebar.
• Accurate URL Mapping: Connect entries to page paths using standard slug and prefix settings or advanced patterns built from short text, short text list, and integer fields.
• Holistic Page Analytics: Combine metrics across all matching Google Analytics 4 page paths and view included paths in the sidebar, so variants, locales, and multiple URLs contribute to a clear entry-level performance view.

For more information, see Google Analytics 4 documentation.

The Live Events dashboard is now available to all Contentful Personalization customers in the Optimization tab of the web app.

Live Events is a real-time event streaming dashboard that allows you to monitor the following incoming SDK events as they happen:

• Track events
• Component events
• Identify events
• Page events

It helps you quickly confirm that your setup is correct, tracking is working, and you can troubleshoot potential issues, as they occur. This helps you move faster and build confidence that your data is accurate from the start.

For more information about the dashboard, see the Live Events page in the Help Center.

Starting April 21st, 2026, Content semantics is available on all paid plans. This helps you work more confidently with your content by understanding what your entries are about beyond just the words they contain. This includes duplicate detection, contextual suggestions, improved AI-assisted workflows and access to a semantic (vector-based) representation of your content via APIs.

Content semantics is managed at the space-level and must be enabled via Organization settings before features are available.

This release applies to selected spaces where Content semantics is enabled. Features are available in Contentful and Content Management API (CMA). Existing content models, entries, and workflows remain unchanged.

With Content semantics, you can:

• Avoid duplicate content by identifying entries that cover the same topics or ideas.
• Reuse the right content by suggesting relevant entries when you add references and suggested links in rich text to other entries.
• Improve content quality and consistency to scale by using Smart context in your AI Actions.

Learn more with our Help Center and Developer documentation.

Contentful now streams in near real-time API activity logs directly into your cloud storage, starting with Content Delivery API (CDA) logs delivered to AWS S3.

Enterprise Observability is built for engineering and platform teams who need visibility into how Contentful performs as part of their broader stack. Teams can now bring Contentful into the same dashboards, alerting workflows, and incident processes they already rely on.

With Enterprise Observability, you can:

• Stream CDA logs to your AWS S3 bucket every few minutes, without any manual export or polling.
• Ingest logs into the observability tools you are already using.
• Monitor delivery health programmatically via a dedicated status API, or receive email alerts when delivery fails.

To learn more, read our Enterprise Observability documentation.

Taxonomy data (concepts and concept schemes) is now available on the Content Preview API (CPA) at preview.contentful.com.

Previously, taxonomy endpoints were only accessible via the Content Delivery API (CDA) and Content Management API (CMA), requiring customers working with preview environments to combine multiple APIs. With this update, you can now retrieve taxonomy data using your CPA access token.

Why this matters

If you use taxonomy to organize content (for example, generating slugs or filtering by category) in preview environments, you no longer need to mix APIs. You can now use a single CPA token to access both draft content and taxonomy data, simplifying your setup and aligning with best practices.

To learn more, read our documentation.

The Phosphor Icon app helps teams visually browse and select icons from the Phosphor icon library directly inside Contentful, while storing the final selection as structured JSON for flexible frontend rendering.

The app helps content editors, admins, and frontend teams work with icons more easily, without relying on hardcoded enums, opaque token strings, or external documentation. Teams can configure which weights and positions are available, and even limit editors to a curated subset of icons when tighter governance is needed.

Key features include:

• Visual Icon Selection: Editors can search and browse icons directly in Contentful, no need to look them up elsewhere.
• Structured JSON Output: Stores icon selections as structured data including icon name, component name, weight, and position for reliable frontend implementation.
• Configurable Guardrails: Admins have control over available weights, positions, and curated icon sets, so the experience can match each team’s content model and governance needs.

The Operating Hours app helps teams manage weekly business hours through a purpose-built visual editor inside Contentful, while storing the final schedule as clean, structured JSON for flexible frontend use.

This app helps content editors, admins, and frontend teams manage schedules without relying on raw JSON, awkward field sprawl, or brittle content modeling workarounds. Teams can configure where the app appears, choose a 12-hour or 24-hour editing experience, and optionally prefill default hours to match their operating model.

Key features include:

• Visual Weekly Schedule Editing: Editors can manage hours for each day of the week with a clear, guided UI.
• Flexible Day-Level Controls: Supports multiple time slots per day, closed days, and 24-hour operation so teams can model real-world schedules like split shifts, lunch breaks, and weekend variations.
• Structured JSON Output: Stores hours in a predictable JSON shape that is easier for frontend teams to render consistently across store locators, business pages, and other customer-facing experiences.
• Configurable Setup: Admins have control over which content types use the app, whether editors see a 12-hour or 24-hour clock, and what default hours should appear for new entries.

The Link Checker app scans Contentful entries for URLs, validates them via App Functions, and displays broken or risky links directly in the entry sidebar and in a dedicated page-level audit view.

With this app, you can identify broken links, staging URLs, and other risky destinations before content is published. Teams can configure which content types the app applies to, define a current domain for resolving relative links, and set allow and deny rules to keep link validation focused and reliable.

Key features include:

• In-Entry Validation: Editors scan links directly from the entry sidebar while they work to catch issues before publishing.
• Rule-Based Guardrails: Supports allow lists, deny lists, and current-domain configuration to help teams flag risky or non-production links with more confidence.
• Cross-Entry Visibility: A dedicated page-level audit view allows admins and content teams search, filter, and review link issues across assigned content types in one place.

The Closest Preview app now supports configurable preview field IDs, making it easier to use with content models that do not rely on a slug field. Teams can now choose one or more short text field IDs, such as URL, to identify previewable page entries.

In this release, we have also improved the setup experience by scoping preview field options to the selected content types, deduplicating shared field IDs, and restoring automatic exclusion of page-level content types from sidebar assignment.

Key enhancements:

• Configurable preview field IDs.
• Support for URL and other short text field IDs.
• Scoped and deduplicated preview field picker.
• Restored exclusion of page-level content types from sidebar assignment.
• Configuration UI stability improvements.

We’ve updated the Slug field to give you more control over how length is validated.

The Slug field now respects the validation rules defined in your content type. This means you can configure a custom maximum length by enabling the “Limit character count” validation in the “Validation” section, instead of relying on a fixed limit.

Previously, the Slug field enforced a fixed maximum length of 75 characters.

By default, the Slug field now allows up to 256 characters, in line with the technical limit for short text fields. To retain the previous behavior, you can explicitly set a maximum length validation of 75 characters.

The Deep Clone app now supports embedded entry references inside Rich Text fields and adds a new reference selection step before cloning.

Deep Clone has previously let teams duplicate an entry and its linked references in a single action. With this update, the app also follows embedded entry references inside Rich Text content, resulting in more complete and consistent cloning of nested content structures.

This release also introduces a new selection dialog that shows the reference tree before cloning. All referenced entries are selected by default, and editors can deselect any entries they want to keep linked to the originals instead of creating new copies.

Key enhancements include:

• Deep cloning for embedded entry references inside Rich Text fields.
• A reference tree dialog that previews which entries will be cloned.
• Default-select behavior with the ability to deselect specific references before cloning.
• More control over cloning complex content structures while preserving existing links where needed.

Contentful’s Bulk Edit app now includes expanded filtering controls and improved support for reference-based editing, making it easier for teams to manage larger, more complex content models.

With improved search and filtering, clearer table context, and support for editing both single-reference and multi-reference fields in bulk, Bulk Edit now better supports the way customers structure real-world content, including linked SEO entries, categories, reusable components, and related content.

Key features in this update include:

• Improved search, sorting, and filtering controls.
• Reference-based filters for finding entries by linked content.
• Bulk editing for both single-reference and multi-reference fields.
• Entry picker support for assigning existing linked content during bulk edit.
• Reference titles displayed directly in the table and bulk edit flow.
• Inline field type labels in table headers for clearer scanning.
• Improved column visibility controls and table layout.

We have sunsetted the Ninetailed legacy app in March as part of our transition to a more unified personalization experience within Contentful. All new setup and configuration should be done within the Contentful web app, in the organization settings.

What you need to know

• No action required. All existing customers have been migrated to the fully integrated Contentful Personalization dashboard, giving you a seamless, end-to-end workflow without the need to switch between systems.
• You can no longer access or sign up through the legacy app.

To access your metrics and data sources, navigate to the Optimization tab in the organization settings.

For more information on the new setup, see Install Contentful Personalization and Set up Contentful Personalization in the Help Center.

We have released v12 of our JavaScript Content Management SDK, contentful-management.js (CMA.js). This update focuses on upgrading the underlying technical foundations to a more modern JavaScript runtime and module system, improving long-term compatibility with current tooling and platforms.

This update will give us the following benefits:

• TypeScript improvements: Better type inference and clearer error messages for developers using CMA.js in TypeScript projects.
• Performance: Potentially faster runtime and leaner bundles in modern build setups, especially when tree-shaking and ESM are enabled.
• Compatibility: Improved support for current Node.js versions and modern build tools (for example, Vite or esbuild), making it easier to integrate CMA.js into contemporary stacks.
• Maintenance & security: Updated and consolidated dependencies so we can rely on actively maintained packages and ship security and bug fixes more reliably.

You can find detailed migration steps and code examples in our CMA.js v12 migration guide, which explains the breaking changes and recommended upgrade path, and common questions in more detail.

You can now access the beta feature of running AI Suggestions across multiple entries at once.

To access this feature, navigate to our preview center, to start generating entry-level recommendations and the ability to review differences and apply changes efficiently at scale. For example:

• Adapt tone by region - adjust wording to align with regional tone and cultural expectations.
• Translation QA audits - review translated content for clarity, tone accuracy and consistency.
• Brand audits across content - align your content to your brand guidelines for tone and terminology consistency.

To run AI Suggestions in bulk, select the entries from the content table, choose your AI suggestion from the Run AI Action dropdown (including any required options such as target locale), and click Start run.

Review results in AI & Automations → AI Runs, where you can:

• View pending and reviewed entries.
• See field-level suggestions with reasoning and change previews.
• Apply, dismiss or restore suggestions.

For more information, read our documentation.

As administrators, you can now prevent manual edits to SCIM-provisioned users, ensuring your identity provider remains the source of truth for access management in Contentful. This helps reduce manual admin work, prevent access drift, and keep roles and memberships aligned more reliably for organizations using both SCIM and SSO.

Navigate to your SCIM configuration page to enable this capability. Check out our SCIM FAQ page for more information.

We have updated the content model editor to give you more flexibility around the validations you can apply when configuring the Slug field appearance. You can now choose whether a slug field should enforce uniqueness by selecting or de-selecting the Unique field checkbox under the “Validation” section. To ensure consistency with existing setups, uniqueness validation is enabled by default when you select the Slug appearance. You can de-select the checkbox at any time. Before the improvement, the Unique field checkbox was not editable.

You can now see the top assets consuming the most asset bandwidth in your organization, sorted by total usage for your current billing period. Updated daily, available across all plans including Free.

Identify high-bandwidth assets, see which spaces they belong to, and use the data to optimize usage or investigate spikes, all self-serve, directly in the web app.

To learn more, see the asset bandwidth documentation.

The Adobe Marketo Form Selector app is now live in the Contentful Marketplace.

This app syncs Contentful with Adobe Marketo marketing automation account to streamline how forms are managed and embedded across marketing content. Editors can access a complete list of available forms and select the desired one directly within Contentful using a convenient drop-down field. This helps marketing teams ensure accuracy, improve workflow efficiency, and reduce friction while managing website content.

Key features include:

• Automatic form retrieval: All available form IDs and titles are fetched directly from your connected account.
• Dropdown field selection: Select the correct form within Contentful without leaving the entry.
• Reduced manual errors: No need to search dashboards or manually copy IDs, which minimizes typos and inconsistencies.

Install Adobe Marketo Form Selector app to help you with the following tasks:

• Multi-Market / Localized Forms
• Lead Gen Forms
• Gated Content / Downloads
• Event Registration
• Webinar Sign-Ups
• Contact Sales / Demo Request
• Newsletter Subscriptions

Get started by installing the Adobe Marketo Form Selector app from our Marketplace.

The Content model templates app has now been fully integrated into the web app, and is now available as a separate tab in your organization settings. With Content model templates you can duplicate content types across spaces to keep your content model aligned, create versions, and manage changes as it grows.

For more information about Content model templates, see the Help Center documentation.

The Locale Field Populator app is now live in the Contentful Marketplace.

Designed for content creators and localization teams, this app helps teams streamline the localization process by automatically copying field values from a source locale to selected targets, eliminating the need for repetitive manual copy-pasting.

Key features include:

• Automatically copies field values from a source locale to multiple selected target locales at once.
• Works recursively across all populated fields within an entry to ensure no content is missed.
• Ensures brand and message alignment for teams managing content in similar languages like English (US), English (UK), and English (Canada).

Get started by installing the Locale Field Populator app from our Marketplace.

Content Insights app is now live in the Contentful Marketplace.

Content Insights app provides teams with a clear, data-driven view of their content production lifecycle.

This app helps content managers and admins assess the "health" of their content pipeline by overviewing its key metrics. Users can interact with charts and view actionable lists to track trends over time, filter by content type or creator, and get a high-level overview of their publishing velocity.

Key features include:

• Tracking publishing data - View analytics on published content, publishing velocity, average time to publish, and content that needs updates.
• Visualizing content production - Filter charts by date range, content type, and creator.
• Content tracking and management - View and manage scheduled releases, recently published entries, and content flagged for updates.

Get started by installing the Content Insights app from our Marketplace.

We have released v6 of our design system, Forma 36. This update focuses on upgrading the underlying technical foundations to React 19, TypeScript 5, and emotion 11.

This update will give us the following benefits

• TypeScript improvements: Better type inference and error messages
• Performance: Faster runtime and smaller bundle sizes
• Compatibility: Works with modern build tools (Vite, esbuild, etc.)
• Maintenance & security: Some versions of third-party packages in Forma 36 are no longer actively supported. We have updated and/or exchanged these packages for actively supported ones.

You can find detailed migration steps and code examples in our migration guide and FAQ Page

Auto-prefix app is now live in the Contentful Marketplace.

This app automatically generates consistent internal names for Contentful entries based on their parent relationships, helping users save time and maintain standardized naming conventions, especially in complex, nested content structures.

Key features include:

• Automatically populating internal name fields during entry creation using parent data.
• "Refetch” button for easy update or override of generated names.
• Ensuring consistent naming conventions across complex, nested content structures.

Get started by installing the Auto-prefix app from our Marketplace.

All Pro, Premium, Pr+/Enterprise customers who have AI Actions enabled can now run AI Actions in bulk to generate and update content across large sets of entries in a single operation.

Running AI Actions in bulk help teams to:

• Translate large volumes of content into new locales at once, including linked reference entries, making new market launches faster and easier to manage.
• Generate or update metadata such as SEO descriptions and image alt text at scale, improving content quality and discoverability without manual effort.

All outputs remain fully reviewable. Teams can inspect, edit, and approve results before publishing, ensuring accuracy and consistency at scale. This significantly reduces repetitive work while maintaining the control teams need to localize and optimize content with speed and confidence.

For more information, read our documentation.

You can now use Automations to run actions automatically when content changes or on a schedule, helping teams reduce manual work and move content through workflows more efficiently.

Automations let you combine triggers, conditions, and actions such as AI Actions and Automation actions to create practical, content workflow processes. This makes it easier to scale content operations while maintaining consistency and governance.

You can also explore our step-by-step use case tutorials that show how to build and configure automations for common scenarios.

For more information, read our documentation.

We’ve introduced environment-level permission evaluation within spaces. When a user has multiple roles scoped to different environments, their access is now calculated per environment rather than merged across all. This gives admins precise control over access to development, staging, and production, supporting least-privilege practices and reducing the risk of unintended access.

Navigate to Organization settings & subscriptions > Organization information to enable it for your Contentful organization. Check out our FAQ page for more information.

You can now view the Contentful web app and our Help Center documentation in your preferred language. Choose between English, French and German to navigate through the UI in the language that works best for you.

Why this matters

This update helps global teams collaborate more efficiently by reducing friction caused by language barriers and improving the overall user experience.

How to change language preferences

In the web app, you can update your language preference in the Account settings in your User profile. To change the language in the Help Center, you can choose from the language switcher by scrolling to the bottom of the screen.

For more information, visit our docs.

What’s changing:

For customers on the Free plan, when monthly Asset Bandwidth or API usage reaches the plan’s limit, Contentful will now automatically pause delivery APIs (CDA, CPA, GraphQL) until the start of the next calendar month or until the organization upgrades to a paid plan.

For more information, read our documentation.

The Contentful Personalization dashboard is now fully integrated into the Contentful web app, offering you a unified, seamless user journey from beginning to end.

You no longer have to create a separate account in the Ninetailed legacy app and switch between systems to set up your data sources and metrics. It all happens within Contentful.

For new customers, once your organization has Contentful Personalization enabled, you can access the metrics and data sources from the Optimization tab in the organization settings.

For more information on the new setup, see Install Contentful Personalization and Set up Contentful Personalization in the Help Center.

You can now cancel your Contentful subscription directly in the web app, without contacting support.

When a subscription is cancelled:

• Recurring billing will stop, so you won’t be charged for future renewals.
• Your organization will move to the Free plan at the end of the current billing period, and you’ll retain access to your current plan until then.
• You’ll see a confirmation banner in the web app, and a cancellation email will be sent to the organization owner.

This improvement is only available to customers on our Lite plan.

For more information, read our documentation.

You can now allowlist a fixed set of static IPs to deliver audit logs to your storage destination. This helps you align with stricter firewall or network rules that ensures your audit log delivery meets your organization’s security standards.

See the full list of static IPs by data residency region here.

You can now create localized workflows to manage translation and review processes across multiple languages within the same space.

Each workflow can now automatically adapt to your localization settings, assigning the right translator and locale to each language version. This makes it easier to coordinate multilingual content and maintain consistent approval within your workflow.

For more information, visit our Help Center docs and Developer docs.

You can now see how much asset bandwidth each space in your organization consumes on the Asset Bandwidth page of the “Usage” tab in your organization settings. For each space, the dashboard displays usage both in GB (or MB) and as a percentage of your organization’s total bandwidth.

What’s improved With this improvement, you can: View bandwidth usage per space for the current usage period See both absolute usage (GB) and share of total organizational usage (%) Quickly identify high-usage spaces to investigate spikes or optimization opportunities Use space-level data to support internal cost allocation across teams, brands, or regions

Why it matters Previously, the total asset bandwidth usage was only displayed at organization-level, making it difficult to understand where usage originated. Space-level reporting provides clearer visibility and enables teams to investigate high-usage areas directly, at any time.

To learn more, see the asset bandwidth documentation.

You can now use the sec-check CLI command to quickly assess your Contentful organization’s security posture. It runs out of the box with the following check points:

• Permissions
• Audit logging enabled
• Security contact configured
• SSO enabled
• SSO enforced
• SSO exempt users identified
• MFA status for exempt users
• Long-expiry access tokens

Each check delivers clear PASS/FAIL results with actionable data.

Export and automation

• Results can be exported to structured JSON with a single flag -o, making it easy to archive, track changes over time, or integrate with monitoring dashboards. Each failed check includes contextual details (counts, affected IDs) to speed remediation.

Extensible framework

• The check system is designed for community contributions. Add custom checks by following the existing pattern (ID, description, dependsOn, run) and submit a PR. This establishes the foundation for a growing catalog of organization security insights.

For more information about the CLI command, see the developer documentation.

Organization admins now have greater control over how personal access tokens are used within their organizations.

• De-authorize tokens: Admins can now de-authorize personal access tokens created by users in their organization.
• Enforce manual authorization: Admins can require users to manually authorize their tokens against the organization before use.
• For token issuers: When manual authorization is enforced, users creating tokens will need to explicitly authorize them to gain organization access.

These controls help organizations prevent unauthorized token use and strengthen overall security without disrupting existing workflows. Learn more about managing and authorizing tokens in our documentation

We have enhanced AI Actions to support BYOM (bring your own model), allowing you to connect your organization’s large language model (LLMs) provider to Contentful.

The following AI provider connectors are supported:

• OpenAI: Connect models hosted by OpenAI, such as GPT-5 or GPT-4o.
• AWS Bedrock: Connect models hosted on AWS Bedrock, such as Anthropic Claude.
• Google Gemini: Connect to models available on the Gemini API, such as Gemini 2.5 Flash.
• Google Vertex AI: Connect to Google generative AI models through the Vertex AI API.
• Custom model connector: Connect any model that exposes an OpenAI-compatible API endpoint.

For more information about BYOM, see the help center documentation.

Organization administrators can now require two-factor authentication (2FA) for users who are manually exempted from SSO enforcement.

This provides additional protection for collaborators such as contractors, agencies, or temporary users who aren’t part of your identity provider.

When enforced, these users will be prompted to set up and use 2FA the next time they sign in. This update helps ensure that every account in your organization, including those outside your IdP, meets your security standards.

Learn more in our docs on managing SSO-exempt users and 2FA.

The Homebase app by Contentful is now available in the Contentful Marketplace. This app enables admins and editors to feature important highlights, such as team updates, onboarding guides, and quick-reference materials, directly on the Home page.

With simple, Markdown-powered authoring and a seamless editorial workflow, Homebase helps teams create a consistent, welcoming entry point into their workspace — without technical overhead.

Key features include:

• Simple configuration with a single content type and minimal setup.
• Using Contentful editor so non-technical users can intuitively create and maintain content.
• Contentful native versioning and permissions for secure, collaborative updates.
• Built-in Markdown editor to publish rich content with no coding required.
• GitHub Flavored Markdown support to enhance clarity with tables, checklists, strikethrough, footnotes, and more via GFM syntax.

Get started by installing the Homebase app from the Marketplace.

We have released Cloudinary App v 1.3.1. Here's what has been added and improved:

• Integration support by Cloudinary - Cloudinary now supports its integration in Contentful.
• Insert videos through the Media Library Widget - Now you have the option to insert videos from Cloudinary through the Media Library Widget. Apply search filters to view videos, images, or both.
• Dynamic filtering of assets - Cloudinary assets are dynamically filtered based on Contentful field values, using search expressions with JavaScript template literals.
• Access to Cloudinary editors - Access Cloudinary image and video media editors directly within Contentful (in Beta).

For more information, see Cloudinary documentation.

Audit log delivery is now more reliable, with built-in visibility and recovery for failed deliveries. If Contentful can’t deliver logs due to a storage configuration issue (such as expired credentials or permission errors), you’ll be notified and can take action directly in the web app.

What's improved

• Email notifications when delivery or retry fails.
• View failed deliveries from the last 30 days in Audit logs.
• Retry delivery for each failed day individually, once your configuration is fixed.

Why it matters

Previously, failed audit log deliveries weren’t visible or recoverable. You’ll now be notified of issues and can view and retry failed deliveries directly in the web app.

To learn more, see the audit logs documentation.

Customers can now filter search results by locale directly in the content search bar, making it easier to find localized entries and assets.

You can select up to five locales configured in your environment to narrow results. The locale filter applies across all search components, including full-text search, field filters, and asset filters.

When multiple locales are selected, entries matching any of the conditions across those locales are included, unless using filters like “is empty” or “does not contain,” which require matches across all selected locales.

For more details, read our documentation.

The Closest Preview app is now live in the Contentful Marketplace. Built for content editors working with nested or modular content models, this app helps you quickly locate which page-level entry includes the current banner, CTA, or component, and allows editors to view them in context.

Instead of manually navigating through multiple references, Closest Preview finds the link to the closest page-level entry in the content tree. From there, you can instantly open the page in a new tab. If Contentful's Live Preview is enabled in your environment, you can view updates in real-time.

Key features:

• Automatic discovery of the nearest page entry by tracing references.
• One-click access to view the containing page in a new tab.
• Sidebar integration for seamless access during editing.
• Simple configuration for non–page-level editors.
• Preview-ready design that works with existing Live Preview setup.

Get started by installing the Closest Preview app from our Marketplace.

We have just released Timeline, a new Contentful scheduling and previewing capability that allows editors to create, stage, and preview multiple upcoming versions of the same digital experience. Timeline supports evolving content, enabling teams to manage and preview several overlapping campaigns such as Black Friday and Cyber Monday in parallel.

How does it work?

Timeline introduces a new versioning model for entries, allowing each entry to contain multiple scheduled states linked to specific releases. Teams can assign content updates, including assets, to future time points, preview the full page as it will look on a specific date, and share those views for feedback via the preview link.

GraphQL API users

With this release, we have also introduced a new directive, @timeline, into the GraphQL schema. This is not a breaking change but if your internal tooling expects a certain schema, you may need to review how the changes impact you.

For more details about the feature, see the Timeline section in the help center.

Studio Experiences now support content pre-binding, enabling you to easily pre-associate structured content to a visually assembled pattern in Studio.

When using the content pre-binding feature you can quickly re-use and populate a pattern and nested pattern every time you include one in an experience. Content pre-binding reduces the need to manually bind your content and streamlines your workflows.

How does it work?

• In the Studio pattern editor, you can associate content type fields to pattern component properties, optionally assigning a default entry.

• In the Studio experience editor, you can drag a pre-bound pattern onto the canvas. When selecting an entry, or if a default entry was set, entries immediately populate relevant fields.

For more information about the feature, see the Pre-bind content in Experiences page.

Audit logs have been enriched to capture more context when AI Actions or Bulk Actions are used. These improvements enhance traceability by clearly showing what changed, who triggered it, and which entries were affected.

What’s new

• AI Actions enrichment: each AI invocation now logs the affected entry and field, AI model used, and model provider.
• Bulk Actions enrichment: each bulk action event now includes the action performed (e.g. publish), and a list of all impacted entries and assets.

Why it matters

• AI Actions: enables governance and accountability for AI-driven content updates, supporting compliance reviews, internal approvals, and audit traceability.
• Bulk Actions: surfaces all affected content items to help teams reconstruct and verify multi-entry changes with confidence.

For examples and field-level details, see the AI Actions and Bulk Actions sections in the audit logs documentation.

You can now use Custom flags to personalize or experiment with content outside of Contentful, including features, design elements, layouts, or content living in third-party systems.

With Custom flags, you can manage changes without having to replace content entries. Instead of swapping Contentful entries, you can use an ID in your code paired with plain text or JSON to make the change.

NOTE: Custom flags are only available on specific pricing plans. For more information, reach out to your Sales representative.

For more information about working with Custom flags, see the Custom flag change types page and the developer documentation.

Taxonomy localization enables you to localize taxonomy concepts and concept schemes directly within the Taxonomy manager, making it easier to manage multilingual content.

Locales are automatically sourced from any space in your organization. If a locale exists in at least one space, it becomes available for use in taxonomy. You can select a locale and add translations to localizable fields like preferred labels or descriptions.

Once added, localized content is visible in the Taxonomy manager by selecting a locale from the dropdown next to the search bar.

For more details, see the documentation.

The Native external references feature is now supported in the Content Delivery (CDA) and Content Preview API (CPA). To enable the feature, simply include the externalReferences=* query parameter in your requests.

With Native external references you can integrate content from external sources using the Contentful App Framework. This feature removes the need to make two separate requests (to Contentful and the third-party service), and it handles synchronous delivery.

For more information about the feature, see Native external references and the developer documentation.

You can now build experiences in Studio with a focus on mobile devices as a primary channel with mobile-first breakpoints. When building out your pages, you can use mobile-first breakpoints to define at what screen width your design is displayed on your user’s screen, making sure your webpage is properly rendered.

This improvement makes Studio a true multi-channel experience builder.

To enable defining breakpoints with a mobile-first strategy, update your SDK version. For more information, see the documentation for an example definition.

We have released v5 of our design system, Forma 36. This update introduces a refreshed look and feel, updated components and accessibility improvements.

New look and feel

• Modernized typography and styling across all components.
• Updated to align with our latest design vision.

Icons

• Switched from custom icons to Phosphor Icons.
• Smaller package size and less design overhead. Learn more

Font

• Adopted updated font styles for improved readability and consistency.

Updated and new components

UsageCard (with UsageCount) for displaying usage data and analytics.

• Expanded component library with improved consistency. Learn more

Navbar

• Restyled to a cleaner, lighter design with a single-line structure.
• Environment switcher moved to the right and improved for responsive layouts.

Layout

• Replaced the Workbench with a simplified, hierarchy-focused layout.
• Unified structure across the platform for better focus and readability. Learn more

Improved accessibility

• Enhanced color contrast, larger interactive areas, and better keyboard navigation.

The Rich Text Versioning app is now live in the Contentful Marketplace.

This app gives customers a fast, reliable way to compare changes in rich text fields before publishing. It also helps content creators quickly and confidently review changes in their rich text fields before publishing.

With a Compare versions button directly into the entry editor, users to review current content side-by-side with the last published version. Content changes like additions, removals, and modifications-including embedded entries and asset-sare highlighted so you can publish with confidence.

Key features include:

• Side-by-side diff view of current and published rich text.

• Clear highlighting of added, removed, or modified text and embeds.

• Powered by a proven open-source HTML diff engine.

Get started by installing the Rich Text Versioning app from our Marketplace.

We have released a new SDK version for Studio that brings a major upgrade to the canvas editing experience for designers and marketers building rich digital experiences.

This update improves overall usability and performance, laying a more flexible foundation for future features.

Key enhancements include:

• Panning and zooming: Users can now pan and zoom on the canvas, offering more control and ease when working on long or complex pages.
• Improved node interaction: Upgraded hover and active states make it easier to identify and select nested layers, ensuring more accurate navigation and layer management.
• True WYSIWYG: Components are now rendered as they appear in preview, without structure‑breaking wrappers.

Update your SDK version to access these improvements.

The Deep Clone app is now live in the Contentful Marketplace. This tool is ideal for content teams that frequently reuse structured content layouts, like product pages or editorial templates.

Deep Clone replicates an entry and all of its linked references with one click, so you can spin up new content faster and with complete consistency. No need to manually recreate nested structure, just configure and clone.

Key features include:

• One-click deep cloning of entries and their entire reference trees.
• Flexible configuration to control naming, behavior, and applicable content types.
• No external dependencies fully self-contained and ready to use.

Get started by installing the Deep Clone app from our Marketplace.

The Braze app is now live in the Contentful Marketplace. This enhanced integration helps users send structured Contentful content directly to Braze using "Content Block" syncing.

The app eliminates manual copy-paste workflows by auto-generating Braze-ready content links and sending synced content directly into Braze Content Blocks with locale and field control.

Key features include:

• Sync Contentful content into Braze Content Blocks or via Connected Content links.
• Choose locales and fields to send.
• Secure configuration via API key or OAuth.

Get started by installing the Braze app from our Marketplace.

Starting July 24, 2025, AI-powered taxonomy assignment to assets will be available for Lite and Premium customers.

This feature is enabled in conjunction with AI-powered taxonomy assignment to entries via the Preview center. This allows you to automate assigning concepts to assets in addition to entries to help enhance your content organization and discoverability processes.

Navigate to the "Taxonomy" tab in the asset editor, click Assign with AI, and review the suggested concepts.

You can assign up to 50 AI-suggested concepts to an asset with the option to regenerate AI-suggested concepts.

For more information, read our documentation.

The Iterable app is now available in the Contentful Marketplace. It auto-generates dynamic content links for any Contentful entry, which can be used in Iterable Data Feeds.

This ensures your campaigns always pull the latest Contentful-managed content without manual effort.

Key features include:

• One-click generation of entry-specific data feed URLs.
• Live content sync into Iterable campaigns.
• Simple setup with no manual copy-paste.

Get started by installing the Iterable app from our Marketplace.

As an administrator, when you enforce SSO for your organization, we now apply it for organization owners as well. You can always choose to manually exempt users should you need to.

Check out our FAQ documentation on SSO enforcement to learn more.

Starting July 10, 2025, Contentful audit logs can now be delivered to Google Cloud Storage, alongside existing support for AWS S3 and Azure Blob Storage. This enables teams using Google Cloud to seamlessly integrate Contentful’s audit logs into their observability, security, and compliance workflows.

Audit log delivery now supports the three most widely used cloud storage providers globally.

For details, see the audit logs Google Cloud configuration documentation.

The HubSpot app is now live in the Contentful Marketplace. This app connects Contentful entries to custom HubSpot modules, removing the need to manually sync content between platforms.

With full field mapping, localization support, and in-app content visibility, it streamlines content delivery into HubSpot emails and automations.

Key features include:

• Sync plain text, media, rich text, dates, and more to HubSpot.
• Customize module names and support localized fields.
• View all synced entries and fields from within Contentful.

Get started by installing the HubSpot app from our Marketplace.

The Klaviyo app is now live in the Contentful Marketplace. This app automatically syncs content and customer data from Contentful to Klaviyo, mapping entry fields across platforms to eliminate manual duplication and keep your campaigns up to date.

Key features include:

• OAuth-based secure connection between Contentful and Klaviyo.
• Field and locale mapping to match your data model.
• Content syncs automatically across assigned content types.

Get started by installing the Klaviyo app from our Marketplace.

Contentful's Bulk Edit app is now available in the Contentful Marketplace. The app is designed to help content creators and editors make quick, consistent changes across many entries, the app streamlines high-volume tasks and minimizes manual errors.

With entry filtering, table-style side-by-side comparisons, and the ability to preview edits before saving, Bulk Edit makes it easier than ever to update fields, clean up content, and accelerate editorial workflows, whether you’re editing one field or one hundred.

Key features include:

• Entry filtering by content type.
• Bulk editing for short text, number, or single reference fields.
• Side-by-side comparisons in a clean, table-style view.
• Preview changes before saving.
• Simplified content cleanup for better consistency.

Get started by installing the Bulk Edit app from the Marketplace.

You can now subscribe to Comment Save events using both Webhooks and App Events! This new event type lets you trigger workflows or perform automated actions whenever a comment is updated on an entry.

Comment Save events are triggered when:

• A comment is resolved in the webapp
• A comment is updated, or resolved via API

Whether you're building integrations, notifications, or moderation tools, this opens up more possibilities for interacting with your editorial workflow in real time.

Starting June 5th, each concept returned by the Taxonomy API will now include information about its associated Concept Schemes directly in the response. This makes it easier to identify which scheme a concept belongs to without making additional API calls.

The response payload now includes a conceptSchemes field containing Link objects:

For more information on Taxonomy and its capabilities, please refer to the documentation.

We're introducing automated usage alerts to help you stay on top of your asset bandwidth consumption.

Now, organization owners and admins will receive email notifications when usage crosses 75%, 85%, and 100% of your included bandwidth, so you can take action before surprises happen.

This new capability helps you monitor usage more easily, plan ahead, and avoid unexpected overage charges.

We’re rolling this feature out gradually. Some customers will begin receiving alerts now, with full availability following shortly.

Learn more about usage alerts and bandwidth thresholds.

We have improved the search functionality of the Contentful web app with the ability to search for content stored within JSON fields. This improvement allows editors to easily find specific content that previously could not be retrieved via the search bar.

This feature will be rolled out gradually to customers over the coming weeks. For more information about the search functionality, see the Content search page.

Starting April 24th, our content search bar now includes a filter option for fields that are empty (contain no content) or not empty (contain content), making it easier to find entries missing key information.

This filter is available for all Text (including Symbols), Date, and Number fields.

The GraphQL Content API now supports the ability to retrieve third-party content within the same Contentful payload. When an Entry contains a reference to external content, Contentful natively resolves the External Reference and delivers the content data from the third-party service rather than responding with only a reference.

This feature removes the need to make two separate requests (to Contentful and the third-party service), and it handles synchronous delivery. By making a single request to Contentful that contains data from both sources, link resolution in GraphQL API enables efficient code, reduced overhead, and easier content management.

For more information, see the Native external references Native external references help page and the Native external references section on the GraphQL API page.

Contentful now offers AI Actions to automate repetitive tasks, such as translating content, optimize keywords for SEO, and generating alt-text—directly within your workflow. AI Actions let you configure AI-driven processes that can reference existing Contentful content or integrate external data. With customizable templates and variables, this feature reduces manual effort and helps deliver high-quality, accessible, and consistent content faster.

Key benefits:

• Boost Efficiency: speed up content production by automating translation and SEO tasks, reducing reliance on external agencies.
• Contextual Intelligence: enable AI Actions to leverage your Contentful data or external sources for more relevant outputs.
• Flexible Customization: tailor AI Actions to fit your specific use cases, ensuring the solution works precisely for your content needs.

Availability:

• AI Actions are available on select plans. For more details, please read our AI Actions documentation or contact your sales representative.

Starting March 31, 2025, users can now add AI Actions to workflow steps for specific plans. By integrating AI Actions into a specific workflow step, the system can automatically perform tasks at that step, streamlining content processes. This allows users to leverage the power of AI while still keeping humans in the loop for oversight and review.

Key benefits

• Automatically leverage the power of AI for content lifecycle tasks.
• Enable oversight and review of AI output to reduce risk.
• Reduce the time for completing content workflows.

Reach out to your Sales representative for more information about feature availability.

Starting March 21st, customers of the taxonomy feature will now be able to retrieve taxonomy concepts and schemes via the Content Delivery API.

This will allow customers to leverage their taxonomy directly in user-facing applications, providing tools to better structure as well as filter hierarchical content for their customers.

For more information, customers can reference the documentation for the taxonomy CDA endpoints and client SDKs.

You can now organize related fields into distinct, manageable groups with Sections. Each section can be configured to be either expanded or collapsed by default, enabling you to focus on the information that matters most.

Key benefits

• Improved editorial experience: Grouping related fields reduces visual clutter and makes the editing process less overwhelming.
• Enhanced navigation: Quickly expand or collapse sections to access exactly what you need without distractions.
• Ideal for complex content types: Perfect for content types with numerous fields, Sections streamline your workflow and improve overall content management.

NOTE: This feature is only available on specific plans. Reach out to your Sales representative for more information about feature availability.

For more information about how you can use field groups with Sections, see the Set up field groups page in the help center.

Starting April 21st, 2025, we are switching to RE2 as our regular expression engine, specifically the RE2JS npm package. This will enforce stricter validations for regular expressions in the Content Management API (CMA). From this date, you will no longer be able to publish entries with any regular expressions match or prohibit rules that are not accepted by the regular expression engine.

The previous date for this change was March 21st, 2025, however, to accommodate our customers' needs, we are pushing the date. For more information, see the previous changelog, and the Regular Expression (Regex) page.

You can now sort entries or assets by various criteria in the reference field selector search. You can choose how to order entries using the updated “Sort by” dropdown. This change provides flexible options so you can quickly find the right content.

Note that if you choose a different sorting option than relevance-based, your choice is remembered, and used for future searches.

Viewing Non-Localized Fields in Single Locale Mode

Previously, non-localized fields were hidden in the editorial interface when selecting a single non-default locale. To provide a more intuitive experience, these fields will now always be visible, regardless of the locale you’re viewing. This update makes content management more predictable and aligned with Locale-Based Publishing.

Adjusting Asset Validation in Locale-Based Publishing

We’ve refined asset validation within Locale-Based Publishing. Initially, publishing an asset required a file upload for every locale—an approach that was inconsistent with the Content Delivery API. To align with expected behavior, only the default locale now requires a file upload for publishing. These improvements create a more consistent localization workflow.

Starting February 14th, 2025, Contentful will allow users to mark taxonomy validations as required on content types.

Once a particular taxonomy validation has been marked required for a given content type, any entry of that content type will be checked on publish to determine if the entry has taxonomy concepts assigned which fulfill the required validation(s) from the relevant content type.

Content editors will be given cues in the UI to allow them to easily fulfill any unfulfilled taxonomy validations before publishing.

Starting February 15th, 2025, Contentful now allows up to 50 taxonomy concepts to be assigned to a single entry (previously limited to 10).

This new limit also applies to AI-powered taxonomy assignment feature.

To learn more, read our documentation.

Starting in the afternoon of February 6th, 2025, the CMA will support marking taxonomy validations as required on content type metadata.

Once a particular taxonomy validation has been marked required for a given content type, any entry of that content type will be checked on publish to determine if the entry has taxonomy concepts assigned which fulfill the required validation(s) from the relevant content type.

To make use of this feature, a new required boolean property on the link to the taxonomy concept or concept scheme can be sent in POST, PUT, and PATCH requests for content types.

Once the feature is live, this new property will always be returned on the content type and defaulted to false.

Documentation for the Content Type endpoint can be found here

Starting February 7th, 2025, you can filter by multiple content types when searching within the reference field selector. This makes it easier to find and select relevant entries across different content types.

You can now upload assets with file names that contain Unicode supported script characters, including non-Latin scripts (e.g., 日本語, кириллица, العربية).

The benefits of this update:

• Better localization – You can use file names in native languages without workarounds.
• Easier organization – Keep meaningful file names without forced transliteration.
• Full API and UI compatibility – Works across Contentful without restrictions.

This update is now live for all newly uploaded assets.

We have updated some webhook payloads to include additional properties. Specifically, the publish events for relevant entities will now contain the publishedVersion property. Additionally, unpublish and delete events for relevant entities will now contain a deletedBy property. This deletedBy property has also been added as a webhook filter, so users can now use the deletedBy User ID for filtering which webhook entities will be triggered when configuring a webhook. For more details, see the webhook overview in the developer documentation.

Starting Jan 31 2025, APIs for managing Functions are now available as a part of the ongoing App Action and App Event Functions Beta (join the beta via the preview center) and for use in Native External References and Custom External References which are generally available. Learn more about Functions.

Similarly, APIs for retrieving Function Logs are now available as well. This API allows the retrieval of Function Logs programmatically in addition to logs which can be searched and viewed in the App Details screen of the Contentful UI.

Starting February 17th, 2025, we are releasing an update to resolve an issue where the query complexity was miscalculated when the limit argument was set to 0. The original date for this update was February 4th, 2025. However, to accommodate our customers' needs and give them more time to make any necessary changes, we’re adjusting the launch date.

Important: This is a breaking change.

See our previous post for more details.

Starting 17th February, 2025, the GraphQL Content API will support the Embargoed assets feature for relevant customers. The original date for this update was February 4th, 2025, however, to accommodate our customers' needs and give them more time to make any necessary changes, we’re adjusting the launch date.

See our previous post for more details.

You can now join the beta for our App Functions directly from the Preview Center, by logging in to the Contentful web app, clicking your account menu, and enabling the feature for your organization.

What are App Functions?

App Functions are a powerful capability of the Contentful App Framework where development teams can use Functions to execute serverless code on the Contentful platform, removing the need for dependence on external infrastructure.

For more information about Functions and how you can use them, see the developer documentation.

AI-powered taxonomy assignment is available for Lite and Premium customers. Our AI taxonomy assignment feature is now accessible via our Preview center. This allows you to automate assigning concepts to entries to help enhance your content organization and discoverability processes.

Navigate to the "Taxonomy" tab in the entry editor, click Assign with AI, and review the suggested concepts.

You can assign up to 50 AI-suggested concepts to an entry with the option to regenerate AI-suggested concepts if needed.

For more information, read our documentation.

Starting March 21st 2025, we are switching to the regular expression engine RE2. This will enforce stricter validations for regular expressions in the Content Management API (CMA). From this date, you will no longer be able to publish entries with any regular expressions match or prohibit rules that are not accepted by the regular expression engine.

We are switching to the RE2 engine as it provides more security and better performance compared to the regular engine.

What you need to do:

To continue publishing entries with offending regular expression validation rules, you need to rewrite these regular expressions and check if they are accepted by the new engine.

One way to do that is to try it out on this Playground, or you can make sure it does not include anything listed in the unsupported rules of RE2.

Starting 4th February 2025, the GraphQL Content API will support the Embargoed assets feature for relevant customers. This enhancement extends the functionality of embargoed assets, allowing authenticated access to restricted assets directly through GraphQL queries.

Embargoed assets restrict public access to content by requiring that all requests include a dynamically generated signature. When enabled, these assets are served from the ***.secure.ctfassets.net domain.

For more details, see the Embargoed Assets page and the Asset keys section of the GraphQL API page.

We have upgraded Contentful’s search functionality, making it easier than ever to find content by URLs. Customers can now search for full URLs, partial URLs, and URL components within entries, across all regular text and rich text fields.

How does it work?

For example, given the URL: https://www.contentful.com/help/content-and-entries/content-search?some_param=some_value

You can now search for:

• Parts of domains, i.e. subdomains and domain names (e.g., www, contentful).
• Partial paths, with or without the leading slash (e.g., /content-and-ent, content-search).
• URL parameters and their values (e.g., some_param, some_value, ?some_param=some_value).

Searches like the following will now work:

• contentful.com/help/con
• content-and-ent
• /content-and-en
• some_param
• ?some_param=some_value

This update is being rolled out progressively, so look out for it becoming available this week. For more information about search capabilities, see the Content search page.

On February 4th 2025, we are releasing an update to resolve an issue where the query complexity was miscalculated when the limit argument was set to 0.

After this update:

When the limit is omitted or explicitly set to 0, a default limit of 100 will apply.

This change ensures consistent behaviour across all Contentful APIs, including GraphQL API, Content Delivery API (CDA), and Content Preview API (CPA).

What you need to do:

We recommend reviewing any queries that use a limit of 0 to ensure they align with this updated behaviour. This only affects a very small number of our customers who have also been notified via email.

See GraphQL Content API - Complexity Limits for more details.

Locale-based Publishing is now available for Premium customers. This update enables content teams to independently publish content to specific locales, giving organizations more autonomy over their international content operations.

Teams can now manage publishing schedules per locale, allowing for market-specific content timing. Content managers can select which locales to publish to, while not affecting or updating other locales. This feature supports sophisticated international content strategies by enabling precise control over when and where content goes live.

Starting today (November 21, 2024), the CMA will support user-defined Resource IDs on newly created taxonomy concepts and schemes.

To make this feature possible, the CMA will now feature two new PUT endpoints for taxonomy, which can be provided with a parameter for the desired concept or concept scheme ID:

• /organizations/{organizationId}/taxonomy/concepts/{conceptId}
• /organizations/{organizationId}/taxonomy/concept-schemes/{conceptSchemeId}

Documentation for the concept endpoint can be found here, and for the concept schemes endpoint here.

We are announcing a further postponement of the enforcement of stricter validation for required fields in the Content Management API (CMA) to accommodate our customers during the upcoming busy holiday and retail periods.

The new enforcement date will now be 21st January 2025.

After this date, entries with any required fields left empty will not be publishable, even if these fields are hidden in the field editor. If a field’s validation is set as both disabled: true and required: true but is left empty, a validation error will occur. We will then reveal the hidden fields so that a value can be input.

Thank you for your understanding as we aim to make this transition as seamless as possible. Please reach out if you have questions or need support in preparing for this update.

For more information about the upcoming change and how to migrate, see the Validations for hidden and required fields page and the Content Management API page.

Over the next days, Contentful is rolling out the ability to assign taxonomy concepts to media assets, return taxonomy information on assets, query assets based on taxonomy concepts in the Content Management API and Content Delivery APIs to all customers.

Media assets do not need content type validations to assign a taxonomy concept. All taxonomy concepts created within the organization are available for assignment to an asset.

In the media asset editor, navigate to the “Taxonomy” tab and select concepts to assign to that media asset.

For more information, please read our Help Center documentation, CMA docs here and CDA docs here.

We’re excited to announce the launch of the audit logs feature, providing your organization with a comprehensive solution to track and monitor critical changes across your Contentful organization, spaces, and environments.

Audit logs help ensure compliance with industry regulations, support incident investigations, and enable monitoring of changes in your organization’s setup. Logs are delivered daily to your preferred storage location—either AWS S3 or Azure Blob Storage—in a structured JSON format using the Open Cybersecurity Schema Framework (OCSF). This ensures consistency, security, and ease of integration with your existing monitoring and compliance tools.

This solution helps your teams to gain full visibility into key activities, ensuring that you know who made changes, what changes were made, and when—all critical for compliance, audit readiness, and risk mitigation.

Only organization owners and organization admins can set up and edit the audit logs storage configuration, ensuring that your setup is secure and controlled by authorized personnel.

For more details, read the audit logs documentation.

Version history for Studio is now live. This feature allows users to compare the current version of an experience with any previous published version. Users can view side-by-side screenshots of different versions and restore to earlier versions if needed. This update enhances version control capabilities and provides greater confidence in managing experience deployments.

The Compose app is being deprecated. Installations of the app will no longer be available via the Contentful Marketplace, and current installations will be functional and supported until December 2025.

Why Compose is being retired

When we launched Compose in March 2021, we aimed to support content producers with an alternative to navigating the nested content structure provided in the Contentful web app by offering a simplified, single-page editing experience.

However, we realized this approach was not practical enough of a bridge from structured content to its visual representation. We have learned a great deal from Compose and how we can empower content creators with a stronger connection between content and its visual representation.

Continuity with Live Preview and Contentful Studio Experiences

Based on these learnings, we have two additional offerings that solve this problem in differentiated ways: live preview within the web app and our newest product Contentful Studio Experiences.

Live preview supports a side-by-side visual editing experience with a form editor for content on one side and a preview environment to understand how the content will render on the other.

Contentful Studio Experiences enables the assembly of visual layouts in an intuitive drag-and-drop interface supported by the power of structured content for non-technical teams that need the autonomy to produce the visual outputs of their content experiences.

We have great things on the way as a result of what we learned with Compose. We received lots of feedback from users about how much they enjoyed the whole page publishing functionality in Compose, and have migrated this functionality into both live preview and Contentful Studio.

Next steps

We are currently working to migrate the Field Groups feature into the core web app within the next quarter. This feature is currently available via the Preview Center where users can try it out in the web app.

We will continue to support Compose until the end of 2025. Please contact your Customer Success partner if you need additional assistance on this migration.

As always, you can reach out to us at any time with your questions regarding this change. Our support team is here to help.

The refreshed UI reflects our commitment to modernity. This update helps users navigate the platform more efficiently so they can focus on creating, managing, and optimizing content-driven experiences.

Key changes

1. The navigation is streamlined into a single line, maximizing space for what matters most—your content. It adapts seamlessly to different viewport sizes and features larger click targets for improved accessibility, especially benefiting users with fine motor skill impairments. Enhanced color contrasts and refined semantic HTML further boost accessibility, making navigation easier for users with vision impairments and those relying on assistive technologies like screen readers and keyboard navigation.

2. New page cut and layout focuses visual salience on content and actions, highlighting headers and most important information. It is responsive, adapting to different viewport sizes.

3. The new layout limits the width of field editors to improve readability. If you need more space for your custom editor, you can enable the "Wide editor view" by clicking the three-dot menu in the top-right corner of the page.

We have improved the performance of the web app by implementing cursor-based pagination. This enhancement streamlines the content loading process, providing a faster and more efficient experience for users.

Where can I see the number of entries now?

You can view the number of entries by navigating to the Usage page from the settings menu. Thank you for your understanding and continued support as we work to enhance your experience.

On October 21st, the GraphQL API will support Contentful’s Taxonomy feature. Once the improvement is released, if you are on a premium plan and above, you will be able to filter entries using Taxonomy Concept IDs and even filter by descendants in the GraphQL API. With this enhancement, you can deliver a more personalized and contextually relevant user experience by leveraging structured and categorized content.

In addition, this enhancement allows you to build more advanced content discovery and filtering capabilities using the hierarchical structure of taxonomies. Users can target entries by specific and related concepts, unlocking more dynamic content curation.

Schema changes

We are going to update the schema by adding new types called ContentfulMetadataConceptsFilter and ContentfulMetadataConceptsDescendantsFilter. These new types will allow you to filter on concepts and their descendants.

These schema changes are necessary for taxonomy addition to GraphQL API.

For more information see the Taxonomy section on the GraphQL API page.

On October 21st we are adding new fields to the CDA (Content Delivery API) and CPA (Content Preview API). On the CDA we are adding the following fields to the sys object:

• publishedVersion

Here is an example of a new response:

On the CPA we will be adding the following fields to the sys object:

• firstPublishedAt (only present after an item has been published for the first time)
• publishedAt (only present when the item is published)
• publishedVersion (only present when the item is published)

Here is an example of a new response:

You can use the publishedVersion or publishedAt fields to determine if an entry is published. On a draft entry these fields will not exist.

All of these fields can be filtered. For more information about the available filters, see this page.

What you need to do:

If you have a setup that is dependent on the sys field shape, you will need to update your code to accommodate the new changes. For example: if you access sys fields by their numerical position in the array, this will potentially break for you as the field may be at a different position.

Our CDA (Content Delivery API) support for Taxonomy is currently entering the GA stage for users. We will be gradually rolling out this capability to all users within the next few days. You can now filter entries using Taxonomy Concept IDs, including filtering by descendants. This allows you to deliver a more personalized and contextually relevant user experience by leveraging structured and categorized content.

This enhancement allows you to build more advanced content discovery and filtering capabilities using the hierarchical structure of taxonomies. Users can now target entries not only by specific concepts but also by related concepts, unlocking more dynamic content curation.

What’s now available:

• You can filter entries in the CDA by specific Taxonomy Concept IDs using the [exists], [in], [nin] and [all] operators, similar to how tags are filtered.
• The metadata.concepts.descendants with operator [in] allows you to discover entries that belong to specific concept’s descendants.
• Payload changes: entries now include taxonomy fields, making it easier to retrieve and filter by taxonomy-related metadata in CDA and CMA.

What Hasn’t Changed: Existing filtering methods outside taxonomy, such as tags and categories, remain unchanged.

No impact on users who do not utilize taxonomy in their content model. For more details, read our documentation.

We are excited to add to our earlier App Event function announcement, with our newest type of function: App Action Functions! App functions (both Action and Event) are currently available in beta. You can join the beta via the Preview Center, which you will find under the account menu when you are logged in to your Contentful account.

App Action Functions are a new capability of the Contentful App Framework where development teams can use Functions to execute serverless code on the Contentful platform, removing the need for dependence on external infrastructure.

App Action functions can be called via the CMA and are often triggered by a user interacting with some UI component in your app. For example, a user might click a button that triggers a CMA call to your app action, which is mapped to your function, that can then perform the task defined by the code written in the function. Stay tuned for the next addition to the App Functions Beta: Synchronous App Actions.

Content source maps are now available for live preview. Our APIs now return source maps for certain visual fields that link to the correct field in Contentful. The Live Preview SDK transforms these maps into hidden metadata within query results, enabling a seamless connection between web content and corresponding Contentful fields.

This update makes it easier to setup and use Inspector Mode, enabling content creators to visually navigate and edit content with precision. A clear link between displayed content and fields within Contentful leads to a more efficient content management process.

For more information, read our Developer Documentation

.

We’re excited to introduce a major update to our search functionality with the release of our new search algorithm, which enhances result accuracy and relevance. This release also includes an update to our UI with a new drop-down field that allows users to easily prioritize search results based on their importance. This feature will be rolled out progressively, so stay tuned as we make it available to all customers.

For more information about the search functionality, see the Content search page.

The updated design properties panel is now available for all Studio customers. The design properties panel has been revamped for improved usability. Updates include:

• Better alignment with industry-standard design tools
• Unified expand/collapse patterns across all properties
• A clearer indication of non-default states
• New drag controls for padding, margin, and corner radius.

These changes enhance the discoverability of modified properties and improve overall readability, making the design process more intuitive and efficient.

Introducing the new Native external references feature that allows you to seamlessly integrate content from any external source directly within your content model in Contentful. By leveraging existing Reference Fields and the App Framework, you can link third-party systems and pull content directly into Contentful without having to create a custom front-end app.

This feature is available on Premium plans only.

For more information about the feature, see Native external references and the developer documentation.

As part of this release, the External references feature has been renamed to Custom external references.

TIFF (Tagged Image File Format) is now fully supported in the Contentful web app and Images API. Previously, you could upload TIFF files, but our Images API didn’t support transformation or delivery of these images and they were instead delivered from the files subdomain.

Here’s what has changed:

• TIFF files can be transformed and delivered on our Images API
• TIFF image dimensions are now calculated and accessible via our API, and they are displayed in the list of media assets.

Leveraging the TIFF format allows you to maintain high-quality images, which is particularly useful for professional photography and publishing needs. This support ensures that your content retains its rich detail and accuracy across your platforms.

Scheduled publishing is now available for all Studio customers. This update allows users to schedule experiences to be published or unpublished at a specific date and time. Users can set up, edit, or cancel publishing schedules through the Publish options menu in the experience editor. This feature helps to improve content management and timing of experience releases.

For more information, read our Help Center article.

Editable patterns are now available for all Studio customers. This update enables Studio users to make design changes between pattern instances like changing the background color or font size. When creating or updating a pattern, users with the “Edit experiences and patterns” access level can choose if a pattern is editable or remains static. If they choose to make the pattern editable, they can select which design properties to make available to editors. This update increases the reusability of patterns by enabling users to tailor patterns to their specific needs.

For more information, read our Help Center article.

We are excited to announce App Event Function!The feature is currently available in beta. You can request your access here.

App Event Functions are a new capability of the Contentful App Framework where development teams can use Functions (in multiple contexts) to execute serverless code on the Contentful platform, removing the need for dependence on external infrastructure.

App Event functions come in three flavors:

• Filter functions - designed to filter out unneeded app events.
• Transformation functions - designed to modify the structure of an app event before processing.
• Handler functions - allow apps to take action based on the received event.

All three functions also include access to an authenticated contentful-management.js client, allowing function code to read and write back into Contentful using the App Identity as needed. Check out examples here.

When setting up permissions for roles in a space, administrators can now configure publish actions, separately from unpublish actions. This ensures that your users have better guardrails around how they work, and can prevent them from accidentally unpublishing entries.

Your existing rules will remain functional and no action is required on them. Any new rules that you set up for your roles, will allow you to configure these actions independently.

You can learn more about setting up roles and permissions here.

Contentful Apps were unable to subscribe to some events, and some events were not firing correctly. Some events were being emitted via webhooks, but were not available for app developers that would build on top of those events, another group of events were firing unreliably.

App developers can now subscribe to the following events:

• Worflow.create

• Workflow.save

• Workflow.complete

The following events are now emitted reliably:

• Comment.create

• Comment.delete

You can now experience early Contentful features by self-activating/de-activating preview (Alpha and Beta) features and provide feedback.

This will enable you to provide feedback in the development process on the direction of the product by gaining early access to new features.

You can find the Preview Center by selecting your user profile.

You will see a list of all the available preview features. Selecting a feature will show you the release stage of the feature (Alpha or Beta), a description, and a screenshot of the feature. Select the feature you want to try out, accept the Terms of Service, and the feature will be automatically activated.

Every preview feature has one of the following three scopes: organization, space, and user. If the preview feature has an organization scope, only an organization administrator can activate/deactivate the preview feature.

Only the space administrator can activate/deactivate the preview feature for space-scoped features. For user-scoped features, users can activate/deactivate the preview features themselves.

You can also provide feedback using the “Send Feedback” link in the preview description.

After trying out the feature, you can deactivate the preview feature.

You can read about the feature preview in the Help section of the Preview Center. You can read more about the preview features on the Contentful website.

NOTE: Contentful preview features are not ready for production, expected to contain defects, bugs or errors and are not expected to operate at the level of final, generally available offerings. Contentful preview features may be substantially modified prior to general availability or withdrawn at any time. Please read the Terms of Service for preview features on the Contentful website.

The content search bar now includes a descendant search selector for narrowing taxonomy search results. Click on the taxonomy pill in the search bar to choose from the filter options to show content with assigned concepts and their descendants:

• Exact match: This option will populate results for content that has assigned concepts matching the term exactly.
• Include one of: This option will populate results for content by searching for assigned concepts or any of its descendant concepts.

For more information, read our documentation.

We have added support for cross-space link resolution in the Content Preview API allowing you to retrieve resource links from different spaces in a single API call. You can now use cross-space references without having to make multiple requests to retrieve entries that reference other entries stored in a different space. This improvement simplifies your workflows, reduces the complexity of your implementation, and increases efficiency and performance.

In addition, the Cross-space references feature is compatible with the EU data residency add-on.

For more information, see the Resource Links section on the Content Preview API page and the FAQs.

We are announcing a postponement of the enforcement of stricter validation for required fields in the Content Management API (CMA). The new enforcement date is November 14, 2024.

After this date, entries with any required fields left empty will not be publishable, even if these fields are hidden in the field editor. If a field's validation is set as both disabled: true and required: true but is left empty, a validation error will occur.

Important: This is a breaking change.

We have increased the limits of taxonomy concepts from 1000 to 6000 you can assign within an organization.

For more information, please read our documentation.

A Reference Field of a Content Type can now use 20 sources for data; up from the previous limit of 3. This can enable greater flexibility for managing Content Types.

We have updated our implementation of the SCIM API to enable deprovisioning of users. This allows enterprise organizations to remove users from Contentful without having to sign in to our webapp. Removing users from your IDP will now automatically remove them from Contentful, once SCIM is enabled.

You can find detailed information on how to use the SCIM API in our FAQ and documentation pages.

To enhance clarity and reduce confusion, we have updated the Disable in response label to Omit from API response in the content type field settings. When used, this option prevents selected content from being fetched by the Content Delivery API and Content Preview API response, while still being editable in the web app.

We enhanced the GraphQL API by adding support for cross-space link resolution to retrieve resource links from different spaces in a single API call.

You can now use cross-space references without having to make multiple requests to retrieve entries that reference other entries stored in a different space. This improvement simplifies your workflows, reduces the complexity of your implementation, and increases efficiency and performance.

For more information, see the Resource Links section on the GraphQL API page and the FAQs.

Starting November 14th 2024, we are implementing stricter validation for required fields in the Content Management API (CMA). From this date, entries with any required fields left empty cannot be published, even if these fields are hidden in the field editor. If a field’s validation is set as both disabled: true and required: true but is left empty, a validation error will occur.

Scheduled publish actions that meet this criterion will also be impacted.

What you need to do:

To continue publishing entries with hidden fields, change the validation of these fields to optional (required: false).

Contentful Apps have long had the ability to store App Installation Parameters to store critical configuration details, API keys, or other information your app needs. To date these parameters have been plain text json blobs accessible only via API. Today we’ve launched Private App Installation Parameters which adds the ability to configure these parameters via the Contentful UI or CLI and, importantly, introduces a new type called “secret” which obfuscates the value of parameters when a user, rather than an app, retrieves the value. Learn More

Parallel workflows are now available for Premium plan customers. This update allows you to run multiple workflows in parallel within the same entry.

To start a workflow in the entry editor, select a workflow from the dropdown and click the button Start workflow. You can view all of the enabled workflows for the entry in the dropdown. If a workflow is already in progress, the steps will appear in the workflows section of the sidebar.

For more information, read our Help Center documentation.

On June 25th, we are releasing a change to the GraphQL API, that introduces a new interface called _Node which will be used as part of the Cross-space references feature. The interface introduces a new _id field on all ContentTypes.

Example:

This is an additive change, not a breaking change, but it may affect your tooling in certain circumstances (for example, using a linter before builds). We do not recommend customers consume or use this in their applications.

The change is designed to enable cross-space link resolution with the GraphQL API so you can make a single request to retrieve entries that reference other entries stored in a different space. Cross-space link resolution simplifies your workflows, reduces the complexity of your implementation, and increases efficiency and performance.

For more information, see the Resource Links section on the GraphQL API page and the FAQs.

You can now organize, categorize, and annotate content with concepts from a shared taxonomy with Contentful's Taxonomy feature. Concepts represent your domain knowledge in a controlled vocabulary.

Why? Semantically annotated content is easier to discover for consistent reuse across your organization. The taxonomy feature streamlines personalization and prepare content for AI applications. Contentful's Taxonomy feature implements the W3C standard SKOS.

Currently, Taxonomy is in the "GA in progress" stage, which means it is available for 5% of organizations. However, we are gradually rolling out this new feature over the next few days.

You can access this feature by heading over to the Taxonomy manager in the left sidebar, where you can create and edit concepts and concept schemes. Once you have set up your taxonomy validations in your content model, your editorial team can then start attaching concepts to entries as well as search using these concepts.

We’re excited to announce a new platform feature in Contentful, the command palette. The command palette helps users navigate through the platform faster by providing a list of general commands and the ability to execute actions using the keyboard or with the click of a button.

You can open the command palette on any screen within Contentful using the following keyboard shortcuts:

• for macOS: ⌘+K
• for Windows: Control+K.

This update also comes with a change to our quick search functionality. We’ve improved its look and it can now be accessed from anywhere by pressing the / key on your keyboard, or the search icon in the top navigation.

Today, we’re launching a limited set of commands to general availability, with more to come in upcoming releases. If you have any feedback or suggestions to extend this functionality, let us know.

Webhook request verification provides HMAC signature verification for Contentful webhooks. This security layer allows developers to authenticate incoming webhooks and ensure that they originate from Contentful. The feature enables a user to create a Contentful signing secret to hash the request headers and body payload. Subsequently, the recipient server can perform the same process to verify the authenticity and integrity of the data in an incoming webhook.

Learn more about webhook request verification here.

As an administrator of a space, you can now start setting up tailored permissions for Studio Experiences. You can choose from one of the three available presets that provide the users with a viewer, editor or a designer level of access. Additionally, you can also choose specific components for the editors as a means to have more granular control over permissions. You can learn more on how to set up these permissions here.

We enhanced the Multi-region delivery infrastructure (MRDI) add-on feature so you no longer have to use alternate endpoints for the Content Delivery API (CDA) and GraphQL Content API to benefit from it.

With this improvement, there are no more changes required on your side. Once the MRDI add-on is enabled, your system benefits from high availability uptime immediately: Contentful offers 99.99% availability SLA across the multi-region delivery infrastructure. For more information about the MRDI add-on, contact your Sales representative.

We’re excited to introduce significant enhancements to Live Preview. Here’s a concise overview of all the updates aimed to elevate your workflow and boost productivity:

UI Enhancements

• Re-use Counter: Understand whether entries are referenced elsewhere and if so how many times they are re-used.
• Sorting of Preview Platforms: Prioritize your preview platforms.
• Custom Editor Support: Customers who work with a custom editor can now use it with Live Preview.
• Full-Screen Mode: Live Preview now renders full-screen which enables you to see more of preview environments.
• Improved Refresh and Save Logic (Coming Soon): For customers without - SDK live updates, you can now save and refresh with one click, without waiting several seconds to autosave.

Live Updates

• SDK Enhancements: Bug fixes, performance optimization, faster updates, and smaller file size. Please find the technical details on Github. Update your SDK version to access these improvements.
• Third-Party Content Support: Support of external app content (e.g. Shopify)

Inspector Mode

• Cross-Space Reference Support: Users can now also click on links to entries from other spaces.

You can also check if you have the latest SDK version by clicking on the info icon inside Live Preview. Your feedback drives our improvements. Thank you for being part of our journey! 🚀

Multiple workflows are now available for customers in Premium plans. This enables different teams to utilize dedicated workflows for their specific review processes and governance requirements, eliminating the need for a rigid, one-size-fits-all approach.

This flexibility is beneficial when configuring workflows based on factors such as content importance or regional differences. Teams can ensure that workflow and delivery speed are appropriately aligned given the type of content that they need to deliver.

Quickly get started using multiple workflows by navigating to the "Steps" tab within your workflows app. In the "Content types" section select multiple workflows according to your requirements. Detailed setup instructions are available in our help center.

In order to prevent duplication of webhooks, we have introduced idempotent header keys for webhooks. The new X-Contentful-Idempotency-Key header is a unique SHA256 value that is assigned to individual webhooks when fired. In rare cases, webhooks can fire twice for a single action. The new key allows you to set up filtering in your infrastructure to drop a duplicative webhook if the key value matches another very recent webhook request.

We have introduced a new way to interact with the SDK for the Contentful Content Management API - the JavaScript Plain Client and new code snippet examples. This client offers several benefits to developers to save time, reduces redundancy and network calls, and utilizes newer Javascript capabilities like async/await.

• Plain Client allows for the use of async/await with promises, reducing promise chaining that can make code harder to read and maintain
• Fewer calls means fewer network requests, simplifying and speeding your content operations while making mocking simple
• The result is a more ergonomic and predictable development experience with the Javascript SDK and updated snippets

You can use the Plain Client today and view the new snippets in the Developer Portal by opening any operation and selecting the "JavaScript (Plain client)" option.

We’ve made several improvements to Contentful custom apps that help prevent accidental deletion/unsharing as well as provides you more information to manage your apps at scale.

If your app is shared, it cannot be deleted, as deletion would impact other Contentful organizations. Likewise, if an app is listed in the Marketplace, you will no longer have any way to unshare, deactivate, or delete the App Definition until it is delisted. Only Contentful can take these actions, and you can reach out to support if this is needed.

You are also now able to see the number of internal spaces and environments your app is installed in. If you need to uninstall a custom app, you can also now bulk uninstall it in all internal spaces and environments.

We have updated the capabilities of the External references feature (formerly known as Third party orchestration) with a data refresh frequency configuration.

This update allows you to configure the data refresh frequency on fields of Apps that use External References or implement Functions.

By selecting the Resolve content on delivery checkbox you now have the option to configure the Data refresh frequency.

Previously, the Data refresh frequency was not configurable and set to 1 minute by default. If you are using External References it is recommended to update your Content Types to configure the best refresh interval for your use-case.

To read more about this feature and the recommended configuration, see the Data refresh frequency section on the External references page.

As administrators of your organization, you now have the ability to add the email addresses of your security team members who should be notified by Contentful in the event of any security-related incidents. While we dedicate significant effort to safeguarding your data against potential threats, having this information readily available enables us to promptly reach the right people within your organization.

Head over to your Organization settings > Organization information to start listing your security contacts.

You will now be able to use your active session on Contentful to log into the Contentful Learning Center. The Learning Center will no longer require you to log in with a separate set of credentials and will be seamlessly accessible via the Help menu.

To start learning, head over to the Contentful web app and click on the Help > Learning Center.

After March 14th, 2024, the generated GraphQL type for ResourceLink fields will change from a type to an interface and for each field a new type will be generated that implements the ResourceLink interface. The name of the generated type will be derived from the content type name and the field name. For example, if a LandingPage content type has a reference field headline, the new type name will be LandingPageHeadline. If LandingPage has a multi-reference field called testimonials, the generated type will be LandingPageTestimonialsCollection. Additionally, the type field in ResourceSys type will be removed.

The following is an example of a content type LandingPage that has two ResourceLink fields, headline and testimonials and it illustrates the change in the generated schema:

Old schema:

The new schema:

This is a breaking change.

In this release, we are introducing multi-select functionality for the content type filter in the search bar. Now, users can filter content by multiple content types, simplifying searches for items belonging to any of the selected content types.

This update also allows users to save views with multiple content types, particularly beneficial for teams focusing on a subset of content types, reducing clutter, and improving workflow efficiency. The release will be gradually rolled out to all plans, ensuring all users can benefit from this enhanced content management experience.

We have increased the tag limit from 500 to 1000 tags per environment, available on all plans. Note that the 100 tag limit per content entry still applies. For more information about limits, see our Technical Limits page.

Team mentions in comments are now available for all plans when users create or respond to a comment in the Contentful web app. Teams are defined by admins within a space. After typing @, you'll see suggested team names in the dropdown. When a team is mentioned in a comment, all team members will receive a notification.

Improved transparency for editors on fallback locales is now available for all customers.

When setting up locales, customers can define fallback locales so that empty locales are filled with the content of another locale. With this improvement, an icon and tooltip appear to inform the user about the fallback. In the case of a fallback chain, e.g. Spanish (Argentina) to Spanish to English (United States), the tooltip will show the next fallback locale rather than the last. In this example the tooltip for the empty field of Spanish will inform the user that it is falling back to English (United States).

The Multi-region delivery infrastructure (MRDI) is now available to EU data residency customers. With this add-on, delivery infrastructure is deployed across primary and secondary regions in the EU, ensuring content redundancy and higher availability. Contentful offers 99.99% availability SLA across multi-region delivery infrastructure.

For more information, see the EU data residency and MRDI page in the Developer Documentation.

We have added support for GraphQL query directives for External references and the Delivery Functions EAP.

When an external GraphQL API exposes directives on the QUERY location, a copy of this directive (with your app prefix) will automatically be exposed on the Contentful GraphQL API.

One of the use-cases that we now support is Shopify's @inContext Directive. This allows localisation of External references from Shopify directly in the Contentful GraphQL query.

Example query:

We have expanded the capabilities of the Cross-space references feature in Rich Text fields. This enhancement opens up new possibilities for content architects and developers, offering more dynamic and interconnected content experiences. With this update, you can now:

• Embed references to inline entries from different spaces within your Rich Text fields.
• Use hyperlinks that point to entries from different spaces.

For more information about this improvement, see Cross-space references in Rich Text fields: embedded inline entries, Cross-space references in Rich Text fields: hyperlink to entries and the Rich Text node type validations section on the Content Management API page.

You will now start receiving email notifications for expiring Personal Access Tokens. Depending on the expiry date that was set for your PAT during creation, you will receive notifications at 6 months, 3 months, 1 month, 1 week and 1 day before the token expires. You will also receive a notification once the set expiry date has reached and the token has expired. These notifications allow you to stay ahead of the token's expiry and proactively rotate these tokens in to prevent any downtime for your applications due to expired tokens.

Check out the FAQ page for to learn more about Personal Access Tokens and expiration dates.

The new improvements to managing spaces during contract renewals and space archiving are now available for admins and owners who manage spaces in their organizations of all plans.

• Email notification and in-app banner at the top of the page will appear for admins and owners of an organization that goes through a contract renewal after Contentful provisions an order. The email informs about a 15-day period to manage spaces (usually takes a few minutes only). An additional reminder is sent a week later and one day before automatic archiving of spaces without a renewed license assigned.

• Space action menu in the "Spaces" page now holds all important management actions like Upgrade, Downgrade, Archive, Detailed usage, Delete. The menu shows only options that are applicable for each space considering available licenses and usage in each space.

  Note: Archiving a space is only available after a renewal or downgrade to the Free plan. There will be a 15-day period to manage your spaces. Free and Basic organizations have a Modify button near the license type to perform Upgrade, Downgrade, Archive (if available).

• The "Open tasks" section at the top of the “Spaces” page now also holds renewal tasks. Renewal tasks appear once for each type of a space and communicate how many spaces require an action (upgrade, downgrade, archive, delete) based on the license changes you made during contract renewal. When an admin or owner finishes with managing spaces of a particular type, the task is resolved.

• The archived spaces tab in the “Spaces” page will show your organization’s expired trial spaces and other inactive spaces stored with your account. To archive a space is to make a space inactive. This does not mean the space is deleted. Archiving a space means:

  • Your content is safe. We keep it archived in your account.
  • You can restore archived spaces.
  • Content delivery for archived spaces remains in operation for 30 days after archiving a space.
  • You can not create, edit, or publish the content in archived spaces. To view your archived spaces, select the tab “Archived” at the top of the "Spaces" table.  

For more information, see the Manage spaces article in the Help Center.

The CRNs (Contentful Resource Names) used in ResourceLinks for References across spaces now include information on which environment the entity belongs to by default when the environment is master, or another ID when referencing a new cross-space entry.

This change accommodates the new support for environments when linking to cross-space references, and ensures we are consistently representing the resource link information whenever a new reference is linked.

Old format

crn:contentful:::content:spaces/:spaceId/entries/:entryId

New format crn:contentful:::content:spaces/:spaceId/environments/:environmentId/entries/:entryId

You can now merge entries differences between environments right from your command line.

Note: The environments must be within the same space.

To merge content between two environments:

1. Install the contentful-merge CLI.
2. Use the CLI to generate a changeset with the create command with the source and target environments defined. The changeset has a list of added, deleted and edited entries.

3. Use the CLI to merge the changes with the apply command with environment defined.

The command applies changes from a changeset, generated earlier by the create command. It then reports which changes were successful.

Note: The contentful-merge CLI is currently in beta. While we are developing this functionality, we would like to hear your thoughts and suggestions about the contentful-merge CLI and the way you use environments. To see full reference for Contentful Merge, refer to the GitHub documentation.

The improved content and media tab are now available to all customers. Customers can switch between the new and legacy experience via a global toggle in the sidebar of the pages.

The improved content and media tab optimize the view management experience by making it easier to create, manage, navigate, and share views. It provides pre-built views like “Recent” which help the user quickly access recently viewed or edited content and assets. Users are able to define their own views which makes it easier for them to surface priority to their own workflows.

We will be improving the content and media tab experience gradually through October and are aiming to phase the old experience out in the middle of November 2023.

The Contentful GraphQL API has been improved to support automatic persisted queries. This improvement brings the following key benefits:

• Greater Request Size Limit – Using persisted queries allows you to overcome the 8 kb request size limitation and send requests up to 16 kb to create bigger, more complex queries.
• Optimized Network Usage – With persisted queries, you reduce network usage since you only send the query string instead of the entire query. This not only conserves bandwidth but also improves the efficiency of data transfer.
• Faster Response Times – Persisted queries allow for efficient query caching, resulting in faster response times. Frequently used queries are stored, eliminating the need for retransmission and reducing server load.

For further details on implementing persisted queries, see the GraphQL API documentation.

We have rolled out two important updates to the Cloudinary app:

• Selected asset previews in the entry editor have been updated to improve your workflows and confidence while working with Cloudinary.
• External references support with Cloudinary. External assets can now be queried in real-time using our GraphQL API. With this improvement, you no longer need to refresh the asset in Contentful after making changes to it in Cloudinary. The changes are pulled with just one API call.

For more information, see the External references with Cloudinary article in the Help Center.

The Delivery Functions feature has been released as part of our App Framework which can enable External references from any system.

Available now through our Early Access Program (EAP), this powerful new feature executes serverless functions as part of the delivery pipeline on Contentful’s GraphQL API.

You can now define your code to execute and return content with a single request to enable External references. Our CLI tooling fully supports uploading and installing apps as part of common developer workflows to create a seamless experience.

To easily get you started, we’ve created some examples. For all the technical details and how to get started, check our Delivery Functions overview page or our Developer Documentation.

The Commercetools app now supports External references and comes with an enhanced product detail view directly in the entry editor that ensures smooth workflow and confidence with product selection.

External references is a feature designed to boost both digital teams and developer productivity by taking the pain out of creating, building, and maintaining integrations to third party systems.

You no longer need to make that upfront investment in building out integration layers and can instead focus on creating compelling digital experiences at scale.

For more information, see the External references with Commercetools article in the Help Center.

You can now use the Contentful GraphQL API as a subgraph to take full advantage of the features offered by Apollo Federation. With this integration you can resolve references from other subgraphs and extend Contentful Types. To access all Contentful queries in Apollo Federation, you must first configure your Supergraph to pull from the Contentful schema.
For more information about using the Contentful GraphQL API as an Apollo subgraph, see the Developer Documentation.

This integration is only available to customers in Premium plans. Contact sales to learn more and upgrade to a Premium plan.

Contentful's AI Image Generator is now available to all Contentful customers.

AI Image Generator allows you to generate AI images on demand as well as selectively edit any image using AI. The app can be used to create placeholder images, alter approved assets, shorten feedback loops between content creators and designers, and more.

AI Image Generator can be installed from the Contentful Marketplace. This app requires your own personal OpenAI API key with DALL-E credits.

Users are solely responsible for ensuring that AI-generated content complies with applicable laws, their company’s policies, and OpenAI's Terms and Policies.

When using AI Image Generator, you will now see a button when adding an asset called "Generate AI Image."

Click this button and provide a detailed description of the image you want, then click generate. You will see four options, and can download any of them as well as select one to save.

You will also see a new option on any asset to use AI Select and edit. Click the AI Select and edit button with the ✨ icon, select an area of an image that you want to edit, and describe the changes that you want. Click generate to create 3 edited versions that can be downloaded, saved, or saved as a new asset.

As administrators of your organization, you now have the ability to audit the use of tokens within your organization. The new Token Management view within your organization settings allows you to see a complete list of CMA tokens that have access to your organization.

From this view, you can check when tokens were last used, who owns them and if and when they will expire. You can also search through these tokens using the last four characters to quickly find potentially harmful tokens and take remedial actions to mitigate risk.

These actions are also available via the API and you can check out developer docs here to learn more about the API changes.

Head over to your Organization settings → Tokens page to test out this latest feature and let us know your thoughts.

Contentful's AI Content Generator has been updated to add several new capabilities as well as refresh the user experience.

When using AI Content Generator you will now see:

• A new brand profile section on the app configuration screen, with more robust fields to capture your brand's values, products, voice, and unique characteristics. Providing more brand profile details increases the effectiveness of generated content.

• A new workflow for adding AI generated content that allows you to select an option, select from a field or prompt input, and select the output field. Content creators can also stream generated content in realtime, stop generation at any time, edit or copy generated content, and select when content is applied to a field.

• A new option to Rewrite content. This option allows you to shorten or lengthen content, change its voice, style, or tone, or make any other transformations to it that you need.

AI Content Generator can be installed from the Contentful Marketplace. This app requires your own personal OpenAI API key, and supports both Free and Plus keys.

Users are solely responsible for ensuring that AI-generated content complies with applicable laws, their company’s policies, and OpenAI's Terms and Policies.

Custom preview tokens are now available for customers who localize their website across multiple countries, languages, and/or regions. Until now, content preview settings have only supported locale codes (like en-US), but couldn’t support more complex URL patterns.

For example, if a customer uses example.com for their en-US locale, and example.de for the de-DE locale, there's currently no way to designate that in the content preview settings. Preview localization will allow customers to define locale-specific tokens that can be used in their preview URL settings, enabling them to configure preview settings for more locales and editors.

To get started, open the preview settings for your space, and scroll down to the new “Custom preview tokens” section. Add your tokens in JSON format to the text field (use the “Copy template to clipboard” to auto-generate JSON for your configured locales), and be sure to save your changes.

Then update the preview URL for each content type where you want to use the token.

Your editors will also see and be able to use a locale-switcher in the live preview editor.

Preview localization is only available to customers in Premium plans. Contact sales to learn more and upgrade to a Premium plan. Learn more about custom preview tokens in the Set up content preview tutorial.

Users can now see who else is working on an entry or field with the addition of the presence indicator. This improves visibility so teams can efficiently coordinate content updates without the fear of accidentally overriding another’s work.

The presence indicator for an entry is located in the top right corner. If a user’s avatar is active, it means they are currently working within the entry. Users become inactive after two hours of inactivity and their avatar will disappear from the presence indicator.

The presence indicator for a field is located to the left of the field. If a user’s avatar is active, it means they have the current field selected as well as actively making changes. Once a user deselects a field, they are considered inactive and their avatar will disappear.

This update is rolling out gradually to Basic and Premium customers starting on September 19, 2023.

Building on environments and environment aliases, the Merge app can help your team to incrementally create, test and release their content models by propagating their changes across environments.

With our latest release, the Merge app and the Contentful CLI now also detect and allow you to propagate changes which include field reordering in a content type, both for the creation of migration scripts as well as for directly merging content types in the Merge app.

We also fixed a few bugs in the migration script creation to improve the overall usability.

This is how a change which includes moved fields looks like in the Merge app:

We've rolled out an update to the Contentful Shopify app: an enhanced product detail view directly in the entry editor that ensures smooth workflow and confidence with product selection.

What's new:

• Smoother editing journey: Preview Shopify-related content without the need to leave Contentful.

• Right and rich product insights: View detailed information on your product, variant or collection to feel confident in your selection.

Contentful has expanded its global data residency footprint. You can now store your content and user profiles in the European Union (EU) – instead of the US – to enhance trust and solve your critical security and compliance needs. EU data residency is only available for customers on Premium plans. The EU data residency region consists of AWS Dublin, Ireland, (eu-west-1) as the primary region and AWS Frankfurt, Germany, (eu-central-1) as the secondary region for automatically created backups.

For more information about EU data residency, see the EU data residency page in the Developer Documentation and the FAQs.

You can now use References across spaces to link to entries from different spaces and environments in your organization. To be able to link entries from different spaces, you must first enable the spaces for orchestration and allow your entry to reference other environment-scoped entries.

Set up is easy, simply choose the environments you’d like to use when setting up the reference field in the content type configuration page:

You can then select the source space and environment when adding new references to your entries:

For more information about the feature, see the References across spaces section on the Content Management API page and the Environment support for References across spaces page.

Starting with October 16th 2023, the CRNs (Contentful Resource Names) used in ResourceLinks for References across spaces will include information on which environment the entity belongs to by default when the environment is master, or another ID when referencing a new cross-space entry.

This change accommodates the new support for environments when linking to cross-space references, and ensures we are consistently representing the resource link information whenever a new reference is linked.

Old format

crn:contentful:::content:spaces/:spaceId/entries/:entryId

New format crn:contentful:::content:spaces/:spaceId/environments/:environmentId/entries/:entryId

While creating a new personal access token, you now have the ability to set an expiration date. This lets you define how long a token should remain valid. Once the expiry date passes, the token will automatically become inactive. This allows you to have greater control over your account’s access permissions, reducing the risk of unauthorized access. We have also overhauled the token management page which lists all your tokens on a single page and includes much more information such as creation date, token type, and the redacted token.

Head over to your Account settings → CMA tokens page to test out this latest feature. Check out developer docs here to learn more about the API changes.

Visual Modeler is an interactive functionality that allows you to visually build a content model and easily collaborate on changes with your team members. This capability not only streamlines the entire content modeling process by bringing planning, building, testing, and iterating into a single workflow but also shortens the overall modeling cycle.

Who can use Visual Modeler?

Technical users can leverage the Visual Modeler to construct content types, establish connections between them, and visualize these connections through a graph-based interface. They can effortlessly create or edit fields and gather valuable feedback from the editorial team. This synergy results in a validated and scalable content model that paves the way for efficient content creation.

For non-technical users, Visual Modeler offers a user-friendly and intuitive environment to provide feedback on content models. It also facilitates deeper understanding of content connections and helps editorial teams to ensure their content architecture is simple and easy to use.

Key capabilities

• Build your content models by creating content types and fields directly on the visual board. Easily link content types using reference fields.
• Share specific content types or a full model with your colleagues to help them onboard to the platform, understand the content architecture and share feedback.
• Audit your content model. Browse your content types and easily identify missing connections.

To try out this capability, navigate to your content model tab and click Visual Modeler. To learn more please visit our documentation. Help us further improve this capability - share feedback.

You can now view entries differences between environments right from your command line.

Note: The environments must be within the same space.

To learn how content between two environments have diverged, simply install the contentful-merge CLI and run the create changeset command with the source and target environments defined.

The command compares all entries between source and target environments, creates a changeset file, and renders the following changeset details on your command line:

• Number of entries in both environments
• Number of added entries
• Number of deleted entries
• Number of updated entries

Note: The contentful-merge CLI is currently in beta. While we are developing this functionality, we would like to hear your thoughts and suggestions about the contentful-merge CLI and the way you use environments.

For more information, refer to the Readme.

Third party content orchestration is a feature designed to boost digital teams and developer productivity by taking the pain out of creating, building, and maintaining integrations to third party systems. Customers no longer need to make that upfront investment in building out integration layers and can instead focus on creating compelling digital experiences at scale.

We’re excited to announce that our Shopify app is now enabled for Third party orchestration.

With Third party orchestration enabled – you can now query for content from both Contentful and Shopify all using our GraphQL API – in a single API request.

Our Shopify integration is available today for all our customers.

Read our Third party orchestration guide with Shopify to get started today.

We are excited to introduce a new and improved support page and ticketing experience. The updated Support page includes a link to log into our Support Portal, where you can access our knowledge base and submit your support requests.

To access the Support Portal, you can use the same login credentials that you use for the Contentful Web app. If you are already logged in to Contentful, you won't need to log in again.

This update enhances your support experience. We've improved the knowledge base with a wider range of resources for quicker answers to your questions. Our customized ticket forms cater to different support requests, gathering the necessary information for prompt and effective assistance.

We are introducing more App SDK improvements. From now on field's setValue method will not fire additional onValueChanged event triggered in some cases. This behavior was inconsistent with other methods.

Today, we're introducing several updates and improvements to the App SDK:

• The Content Management API is now exposed as a property of the sdk, and can be accessed with sdk.cma
  • This exposes an initialized plain client, without needing to include the cmaAdapter, reducing complexity for developers using the CMA.
• The Parameters API now accepts customizable types for the installation, instance, and invocation types. sdk.field now exposes a linkType to help distinguish more clearly Entry and Asset links.
• Field names are now exposed on the sdk.field.name property. The dropdown and multi-line components are now fully-supported field editors.

These improvements to the App SDK are available for all customers from today. To learn more, please refer to our documentation.

We have introduced an improved checkout experience. It offers a guided process for selecting a plan and purchasing multiple space licenses. Previously it was possible to purchase only one space license at a time. The new checkout also offers real-time total cost calculations to view the plan’s costs when purchasing multiple space licenses at once.

NOTE: the new checkout experience will be available to organizations created starting July 6, 2023 (this release date). This experience will gradually extend to all other customers.

Please let us know if you have any feedback about this new experience by contacting our support team.

You can now use References across spaces in Rich text fields to link to entries from different spaces in your organization. To be able to link the entry, you must first enable the spaces for orchestration and allow your entry to reference other entries. The linked (referenced) entry is embedded from another space as a block element into the rich text, which allows you to reuse content and ensure consistency. For more information about the feature, see References across spaces in Rich text fields and the Rich text node type validations section on the Content Management API page.

Users are now able to resolve or close comments that are no longer relevant to the conversation. This allows users to declutter their interface by resolving comments that have been addressed or no longer applicable.

To access resolved comments, simply navigate to the top right corner and utilize the new filter option. By selecting "Resolved Comments," you can easily review and reference those closed comments whenever necessary. With this update, we aim to improve comment management, allowing for more streamlined collaboration and efficient workflows.

Read more in our Help Center article.

Now, all customers, especially those who heavily utilize our custom roles functionality, can enjoy improved roles and permission management.

Here's what comes with the update:

• The table views for managing roles and permissions have undergone a revamp. Users can now easily locate and scan through all deny and allow rules associated with content and asset-related permissions, which simplifies role management.
• A brand-new Role Tester feature enables users to troubleshoot and visualize how specific rules contribute to denying or allowing particular actions. Administrators can now address user inquiries regarding access controls, empowering them to provide prompt and accurate responses and easily test user permissions when creating new custom roles.

We're excited to share an update regarding our Workflows app! Previously, closing a workflow would delete its history from the entry, resulting in the loss of previous steps.

Now, the workflow history in an entry is always visible through the “View history”, even after the workflow is completed. You can now easily trace and review all the workflows that have been historically run on an entry.

This small enhancement ensures that you have a comprehensive view of the journey your content has taken, allowing for better analysis and improved transparency.

Workflows are available for Premium customers.

We improved the GraphQL Content API to expand the filtering and ordering capabilities for collections. With this improvement, you can:

• filter any collection, if the reference field has a validation rule that makes it only accept a single content type.
• order any linkedFrom collection, except entryCollection.
• order any collection, if the reference field has a validation rule that makes it only accept a single content type.
• skip over unresolved entries.

For more information about this improvement, see the Relational filtering with the GraphQL Content API section and the GraphQL Content API page.

We are excited to introduce a series of UX improvements to the content type editing experience. With these changes, we aim to offer digital teams a more intuitive and efficient workflow for content modeling.

We simplified the interface, enhanced navigation, reduced visual clutter and introduced more informative visual cues. Here’s what changed:

Content type editing

• Removed the right sidebar and moved the "Add field" button to the bottom of the fields list.
• Content type ID is now displayed next to the content type name in the header.
• Introduced a new compact header with a back navigation button for easy return to the list view.
• Removed the "Edit" button from the header and replaced the “Actions” button with three dots.
• Replaced tabs sub-navigation with the right sidebar sub-navigation.
• Refreshed the fields list with a new look and added localisation status.
• Implemented a new fields list style in the "Groups" section.

Field configuration

• Introduced a new full-screen modal with sidebar sub-navigation for field configuration, replacing tabs.
• Field configuration can now be accessed directly through the "Edit", instead of "Settings".
• Added character limits display during field creation for improved clarity.

Changes are being rolled out gradually, please be aware that you may not see them immediately. Help us further improve your experience - share feedback

References across spaces is a feature by Contentful that allows you to link content across spaces (resource links). Using references, you can improve content reusability and enhance consistency within your organisation.

We improved the Content Delivery API (CDA) so you can retrieve resource links from different spaces in a single delivery API call.

Developers can now use references across spaces without having to make multiple API calls in parallel upon delivery. This new functionality will help you simplify your workflows, and reduce the complexity associated with your content delivery, resulting in increased efficiency and ease of use..

For more information, see the Resource Links section on the Content Delivery API page and the FAQs.

Building on environments and environment aliases, the Merge app can help your team to incrementally create, test and release their content models by propagating their changes across environments. And now, the Merge app supports migration of Field Appearance and Help Text changes across environments! The functionality is available for merging and generating export files. This means you no longer would have to alter merge export files or manually update Editor Field Appearances after merging! It was your engagement and feedback that drove this update. Please do share your feedback on how we could further improve the Merge app to better fit your needs.

Administrators can now exempt external users from having to use SSO to log in to your organizations. When SSO sign-in is enforced on your organization, administrators will now have the ability to quickly view the status of exemptions, exempt, or un-exempt users in just a few clicks. You no longer need to rely on Contentful support to perform these actions.

You can refer to this documentation on how to exempt users from SSO and the FAQ page to learn more about SSO enforcement.

With field-level comments, you can now provide feedback and engage in discussions directly on specific fields within your content entries. Say goodbye to lengthy email chains and Slack threads – now you can collaborate more contextually and efficiently within Contentful. The feature will be gradually rolled out within the next weeks.

Here's what you can expect with field-level comments:

• Seamless collaboration: Leave comments on specific fields within your content, providing feedback, suggestions, or insights. @-mention team members and stakeholders to ensure the right people are involved in the conversation and will receive email notifications.
• Contextual feedback: Direct your feedback to specific fields, making it easier for your team to understand and implement changes.
• Streamlined workflows: Simplify your content creation and editing process with field-level comments. Keep track of discussions within Contentful, eliminating the need for external communication tools. Read the editorial documentation to learn more about field-level comments.

Field-level comments are available to customers in Basic, Enterprise, and Premium plans.

Third party orchestration is a feature designed to boost digital teams and developer productivity by doing the heavy lifting of connecting and making content from everyday systems available for use inside of Contentful. This allows teams to spend more time on creating engaging digital experiences.

Available now through our Early Access Program (EAP), customers can simply ask our GraphQL API for the additional data needed from some of our integrations. This eliminates the need for developers to connect to multiple APIs and juggle different formats to fetch content from these systems. Contentful delivers the right information, fresh, in-context and on request with one API call.

Early Access Program participants can already get started with Shopify today, with more integrations coming soon.

To sign up for the Early Access Program or for more information, see Third party orchestration and the developer documentation.

Live preview is an enhanced editorial experience that enables content editors to see how the content looks side by side with the content fields, in the web app. This feature will be gradually enabled over the next few weeks.

Live preview helps digital teams quickly and confidently fine-tune content, leading to

• Increased efficiency by finding and editing content faster
• Higher content quality and less re-work
• Reduced onboarding and training by making the editorial experience more intuitive

Out of the box, live preview offers an intuitive side-by-side edit and preview experience. Content fields appear on the left, and a preview of the page appears on the right. Customers can change the preview viewport from full-width desktop to a narrow-width mobile view.

When developers integrate our live preview SDK into your web site, it unlocks two additional capabilities for content editors:

• Real-time updates in the preview pane: Test different copy variants and see their effect as you type.
• Inspector mode: Find and edit specific content faster by clicking on any tagged field in the preview pane.

Live preview will be included in starter templates for new customers, starting with the marketing website template.

Read the documentation to learn more about live preview.

We have overhauled the user experience for managing the single sign-on configuration for your organization. Helper texts, prompts, and a more streamlined flow on the configuration page make it easier to set up a configuration from scratch while making changes to an existing configuration much faster. Administrators now also have the ability to deactivate SSO for maintenance or save a draft of the configuration to activate it at a later time.

For more information on Single Sign-on please have a look at our support page.

We now support viewing AV1 Image File Format (AVIF) files in the web app. Before this improvement, you could only upload AVIF files, without previewing them.

Here’s what has changed:

• AVIF image dimensions are now calculated and available via our API, while also being displayed in the list of media assets.
• you can now preview AVIF images in the image file view.

By leveraging the AVIF format, you can improve the overall performance of your website or application by reducing loading times, improving SEO rankings, and enhancing user engagement.

@Mentions in comments is a way to direct a comment to specific users. When you use the @mention feature in a comment, the users you mention will receive a notification that they have been mentioned in a comment. This feature is available when users create or respond to a comment in the Contentful web app.

@Mentions streamlines team communication and collaboration.

• For the commenter - easily get colleagues’ attention without switching tools and increase the likelihood of a response
• For the mentioned - proactively get notified of a comment and easily gain the visibility and context needed to respond
• For developers - eliminate the need to build costly and time-consuming workarounds

Read the editorial documentation or developer documentation to learn more about @mentions.

@Mentions is available to all users.

Building on environments and environment aliases, the Merge app can help teams to incrementally create, test and release their content models. And now, you can use the Merge app right from your command line! Developers will be able to compare content type differences between environments, export a migration script and apply it right from the Contentful CLI, without having to switch over to the web UI.

Show content type differences in the CLI

To view content type differences between two environments, use command:

If the Merge app is not installed in those environments, the CLI will prompt you to install it. If you don’t have installation rights, you will need an admin user to install it for you.

Export differences in a migration file

To download a content type migration script for a target environment, use command:

Apply the migration file using the existing Contentful migration command

To apply the exported migration script to your target environment, use command:

Note: If desired, you can make manual changes to the migration script before applying it (e.g. adding entry transformations).

User documentation can be found here.

We want to continue to make your experience with the Merge app better, and would love to hear your thoughts. Help us improve your experience - share feedback.

A fresh new experience to help your team quickly and more easily achieve their content-related goals!

Here’s a closer look at our new experience:

1. List views in content, media & content model. We reduced clutter and improved scannability by:

• Introducing user avatars and adding more visibility for descriptions and titles.
• Removing entry usage counter from content list. It is still available in your usage dashboard. Additionally, you will be informed when you start hitting the limits.

2. Navigation. More compact with improved visibility of space & environment. Settings have been moved to the right side.

3. Contentful Apps. Compose and Launch and Content model templates are moved to Apps dropdown for easier access.

We want to make sure it is easy for anyone to use Contentful thus we continuously work on making the platform adaptable to the way you work and complete your tasks. We are working towards improving experience across all modelling and editing screens thus temporarily you may see some inconsistencies. Help us improve your experience - share feedback.

We have released contentful.js v10 with enhanced TypeScript support!

With typed queries and responses, developers are able to see the shape of content types & entries right in their code editor! No more context switching, everything they need to develop efficiently is in one place.

Improvements in v10

• Query type support — Autosuggestions based on your Contentful content model allow you to know exactly which search parameters you can use in your requests.
• Chained client modifiers — An option to modify the response shape of your CDA calls, and thus get predictable response type support.

Learn more

• Learn how to migrate to contentful.js v10 in our migration guide.
• Have a look at our tutorial demonstrating the new features.

Share feedback

• Write to us in #general with tag #typescript on our Community Slack.

Today, we’re launching an update to our Single Sign-on experience. As administrators, you now have the ability to set up and manage Single Sign-on configurations for your organization in a fully self-serve manner. You can now update certificates, edit the SSO name, and activate or deactivate restricted mode by yourself, without having to reach out to our support teams.

For more information on Single Sign-on please have a look at our support page.

We are extending the character limit for naming Content Delivery API (CDA) and Content Preview API (CPA) keys from 40 to 67.

This means that as admins you have more flexibility when naming an API key, making it easier for you to adhere to existing naming conventions within your organization. Existing CDA and CPA API keys will not be affected. Content Management API (CMA) keys will not be affected. To learn more about different types of API keys, you can check out Authentication documentation.

Contentful has introduced webhook support for completed content model template installations.

The webhook for this event is a great way to trigger additional downstream actions, such as:

• deploying applications to use content model updates;
• testing code against content model changes;
• notifying your team about the changes.

Webhooks can be accessed in the Webhooks page under the Settings tab in the Contentful web app.

To learn more about the Template Installation webhook event and how to use webhooks in your workflows, see Webhooks.

Workflows are now fully integrated with the Content table. Editorial users can customize the content table by filtering and saving views based on the workflow step the content is in. Try it yourself:

• Add the workflow column to the content table to get an overview of the current content states
• Use the workflow filter to search for content that = or != in a specific workflow step
• Save the relevant view with just one click (e.g. “In progress”)

Read the editorial documentation or developer documentation to learn more about Workflows.

Workflows is available to Premium users.

You can now install an integration to Smartcat from the Contentful Marketplace. This integration allows you to send content to Smartcat for AI and human translation. You can install the application from the Marketplace. You will need an existing Smartcat account to use this integration.

You can now install Incentro's A-sync Localiser app from the Contentful Marketplace. This integration allows for asynchronous publishing of field-level localised entries. You can install the application from the Marketplace. Additional features and locales are available with a separate Incentro subscription.

We are pleased to announce a new security update aimed at providing enhanced protection against potential phishing attacks or malicious activities. As part of this update, processing JavaScript files will result in an “invalidContentType” validation error.

This change has been implemented to safeguard the security of our platform and prevent the distribution of potentially malicious files through our CDN.

For our customers who require continued functionality for their content operations and have a valid use case, we have established a allow-list. If you have any questions or would like to be considered for inclusion on this list, please do not hesitate to reach out to our support team at support@contentful.com.

Workflows enables content teams to keep content flowing across the content lifecycle - from first draft all the way to publication - by ensuring the right people are taking the right actions. The app automates previously manual and error-prone processes to ensure seamless collaboration, editing, reviews, and approvals. To get started:

• Install Workflows yourself or ask your space administrator for help
• Read the developer documentation
• Read the editorial documentation

Create workflows and let them trigger automatically

Define your workflow and choose the content types it should be applied to. Automatically start on all entries of the chosen content type or manually start the workflow.

Automate tasks and keep everyone in the loop when changes happen

Create tasks and notifications for different workflow steps. Choose how your teams or users would like to get notified. Create comments for workflow step changes to capture important information.

Set up governance rules to fit your specific process

Define clear roles and responsibilities for each step and content type, adhering to pre-defined governance models. Determine who needs to be involved when and what actions need to be taken, whether that’s moving the content to the next step or moving it back for further revisions.

Workflows is available to Premium users.

You can now send more Slack notifications to more places with the Contentful Slack app. We've boosted the number of notifications that you can configure to 15. If you've already configured the Slack app, you do not need to change anything, but can now add more notifications to your existing configuration.

New to the Slack app? The Contentful Slack app is a powerful way to keep content teams in the know about their content journey. The Slack app allows you to set up automatic notifications about specific Contentful events so that you can quickly notify collaborators about changes throughout the content lifecycle.

Learn more and install the app in the Contentful Marketplace.

Today, we’re introducing an update to our pricing plans. The new Free plan replaces our previous Community offering as the default plan when you sign up to Contentful.

Upgrading to our new Basic plan allows you to enjoy benefits, such as more roles, locales, access to Contentful support and much more, without having to purchase additional space licenses. The new plans allow you scale better with Contentful as you grow your business.

If you are an existing Community customer, nothing changes for you today and you can keep using Contentful as usual or choose to upgrade to the new Basic plan as needed. If you’re a Team customer, you have the option to keep purchasing additional space licenses as needed.

For more information on what’s included in each of these plans, please visit our pricing page.

When creating a reference field, users can now select content types from a dropdown menu instead of multiple checkboxes. This improvement makes it easier for users to search and select the desired content types, especially when there are multiple options available. It also improves the readability and visibility of the selected content types and the available ones.

For more information about reference fields, see References across spaces and Link content across multiple spaces.

Note that this improvement only affects the user interface of the web app. The underlying functionality remains the same.

We've just published a new app in the Contentful Marketplace - Conditional Fields by Prototyp. The Conditional Fields app helps Contentful administrators customize/extend content types by creating conditional fields that can hide the appearance of other fields. This helps you manage content types that are very similar but not identical to one another and reduces the number of only slightly differing content types that need to be created.

Features

• Show or hide fields based on rules you create
• Add or remove rules on demand
• Minimize number of content types used by applying conditional logic instead of creating a slightly different content type
• Supplementary advanced JSON editor

Get the App

You can install the new Conditional Fields by Prototyp app from the Contentful Marketplace

Today, we’re introducing a custom GitHub Action which facilitates automated deployments of frontend apps for users of GitHub CI.

Read more about our Custom GitHub Action in our documentation or the GitHub repository

You can now use an integration to Kibo Commerce in your Contentful spaces. This integration allows you to select products from your Kibo instance and use them inline with other content in an entry. You can install the application from the Marketplace. You will need an existing Kibo account to use the integration.

In the web app entry editor, "Show disabled fields" becomes Show hidden fields, and in the content type modelling field settings, the "Disable editing" option becomes Hide field when editing. With this small change we aim at better reflecting what this simple option really does.

To disable a field so that it can no longer be edited, we recommend adding a new deny rule in the “Roles & permissions” settings to explicitly deny editing on a specific field. See our revised content modelling basics - field managment help center documentation for details.

Now customers can bring information to future users by adding some text in the dialog box when changing a workflow step (in any direction). This feature allows teams to communicate, share, and review important details or insights without the need to switch between contexts, enabling smoother processes and collaboration.

The most recent comment appears in the workflow sidebar widget, and all comments are available in the workflow history dialog box. You can learn more in our documentation.

Content teams building and editing pages in Compose can now change the order of reference entries by dragging and dropping those entries with the mouse pointer. Until now, it was only possible to move a reference up or down by one position with a dedicated button. This was inconvenient, especially for long lists of references, since it would require a lot of clicks.

In Compose, references are often expanded by default to make it easier to write content for a page. To make sorting easier, we also added a button that collapses (or expands) all references with just one click. This makes it much faster to sort a list of expanded references, or just to get a quick overview of all the entries in a list of references.

*Note: This new button only appears if at least two references exist.

We are enabling editors to use superscript and subscript into their content. This is especially helpful when adding sources, footnotes, formulas or special characters such as the copyright symbol.

This new feature is available for the Rich Text Editor. For existing rich text editor content types, you will need to enable it in the content model under the settings tab. For new rich text content types, superscript and subscript are enabled by default.

With this small improvement, users who are assigned to a task, either directly or through their team, can now reassign that task to another user or team without the need to involve administrators in the process.

For example, if a task is assigned to the team, any user who is part of that team can update the task and assign it to themselves or others. Happy tasking!

Scheduled Actions allow users to schedule publish or unpublish actions for their content. Now, Scheduled Actions are also copied over when creating a new environment based on master or another environment. Only scheduled actions that are in status "Scheduled" at the time of the environment creation will be copied over. Completed or failed actions will not be copied over to the new environment.

Read more about environment resources in our documentation.

Now developers can compare content types, review conflicts and merge changes - all without writing migration scripts! With the use of environments and environment aliases, the Merge app allows teams to build incrementally, test and release digital experiences, and more efficiently iterate over the content model. Merge app means safer and easier onboarding for developers and a quick way of becoming productive with the content model.

• Install the Merge app
• Read developer documentation
• Learn how to integrate it into your CI pipeline

Compare differences between two environments

Use a visual interface for identifying the differences between environments’ content models. Validate your changes and be sure of what you are releasing.

Resolve conflicts and merge

Review potential conflicts and take action to resolve them based on provided recommendations. Safely apply changes from the source environment to the target environment.

Export migrations to integrate into your CI pipeline

Export migrations that are generated based on the content types that you selected. The scripts can be exported without applying a merge in the app and saved in the version control as well as used in the CI pipeline.

Today we’re proud to release Studio as part of an Early Access Program (EAP) for all customers. Studio is a unified editorial workspace inside Contentful that streamlines and automates the day-to-day operations of creating, reviewing, and delivering content for digital experiences. Studio goes beyond creation, assembly, and publishing (formerly part of Compose and Launch) to include other critical aspects of the content lifecycle like workflows and governance.

Studio makes working with composable content intuitive and fast, so content teams can deliver critical projects more efficiently than ever.

Copywriters, editors, designers, and content managers can use a single, intuitive interface to:

• Create and assemble content for any channel
• Schedule and publish multiple pieces of content at once
• Keep content flowing through review and approval workflows to reduce risk
• Work autonomously while in coordination with others

Studio can be installed by space and organization admins from the Apps tab in Contentful, and are installed at the environment level like other apps. The free EAP runs from now until early 2023, and makes Studio available to all customers with limitations on the number of page types, releases, and workflow definitions that can be created.

Learn more about Studio on the product page, help center, and technical documentation.

You are now able to takeover the space home to create custom landing pages using the App Framework. Use it for things like customised onboarding, informational dashboards, reminders and visual workflows!

To try it out:

1. Select the Home location in your App Definition
2. Include a Home location in your app project files (or try out our example app)
3. Install the app in your chosen environments as usual
4. Select the app as your space home (per environment) by going to Space settings > Home > Select your app > Save

Available now for all customers.

Launch app introduced a new way of publishing campaigns and content that are related together. Now, Releases and Release Actions are also copied over if you are creating a new environment based on master or another environment.

Read more about environment resources in our documentation.

Customers already enjoy page-based publishing from within Compose, our app for simplified editing and publishing. But they weren’t able to schedule content to be published at a future date or confirm that the content would publish successfully in the first place.

Now customers using Compose with the customizable content model can schedule a Compose page to be published or unpublished at a future date from within Compose. And to confirm that the page will publish successfully at that future date, customers can use the new "Validate" feature to check for errors on their page, such as empty fields or validation errors. Both features can be found as options under the "Publish" menu.

Compose handles pages as a group of connected content that can be referenced and published together as a unit. Accordingly, this new scheduled publishing feature publishes the page root entry along with all of the referenced entries and assets that are connected to it. In keeping with the customizable content model approach, Compose will not publish any references that are also pages (aggregate roots, in technical terms). Learn more about scheduled publishing in Compose.

If you’re using the legacy Compose content model, learn more about migrating to the customizable Compose content model to take advantage of this and other upcoming new features.

Today, we’re introducing a new capability of our App Framework: App Actions.

App Actions help facilitate automated workflows in the Contentful platform and allow the communication between multiple apps.

Two of our Marketplace apps already support App Actions. If installed, the Slack app exposes an action that sends a Slack message to a specific channel. The Netlify app can be instructed to redeploy a website. Any custom app can now make use of this functionality.

In the future, App Actions will be able to even more than facilitate app-to-app communication. We’ll be adding ways to extend Contentful’s UI in a declarative way through App Actions and integrate tightly with our workflow and automation capabilities. With this release, you’ll already be able to extend our entry list with custom actions, by creating App Actions of the Entries type.

We’re excited to open up this functionality to developers today, as we’ll continue investing in App Actions and the use cases they can unlock. Get started building with our App Action documentation, or check out the additions to the reference documentation for our Content Management API.

App Actions can now be built by every customer, using the App Framework.

Apps can now be installed and managed across multiple environments at a time. This allows apps to access and act on all the space-environments where they are installed in, without the need for a backend app to do so.

This entails new capabilities in the UI and the Content Management API.

The first is bulk app installations. It's now possible to select multiple environments into which an app will be installed.

The second is bulk uninstallations. Choose whether to uninstall an app within the current environment only, or within every environment in the current space.

Third, navigation between app configuration screens. Jump from the configuration screen of an app in one environment directly to that in another environment where it's installed in.

And finally, as a developer, you can now query all the space-environments where an app is installed within an organization. This assumes that the current user has permission to access that environment and the app is installed in said environments. If a user or an app does not have permission, the environment and all the data in that included will stay hidden.

This change is fully backwards compatible: all apps continue to behave as they always have. These capabilities are now available to all customers.

It’s now possible to programmatically manage views and folders using our Content Management API. Views and folders help organize and group content in the web app.

Previously, managing views and folders required manual interaction in our web app. With the addition of the UI Config entity in our CMA, updates to views and folders can now be automated using code. Learn how to create and update a view in our CMA reference documentation

This change has no impact on the behavior of views and folders, or their management through the web app. The new API entity is available to all customers.

The error messages returned when using the GraphQL API have been improved. They now include a documentationUrl property that refers you directly to the error details in the API documentation. Example of the new payload:

These details help you understand why the error occurred and offer a solution. For more information, see the GraphQL Errors Explained section of the GraphQL Content API.

The auto resizer of the App SDK has received an update with version 4.6.0. Previously, the auto resizer only adjusted the height of the iframe to contain elements of that were part of the normal flow. Absolute elements were ignored. This caused issues for dropdowns, tooltips or any other absolutely positioned elements.

With version 4.6.0, you can pass a new option to the auto resizer: absoluteElements. Now, the iframe’s height will automatically increase when a dropdown is opened and would have previously overflown the app’s iframe.

Content tags are great because they can be used for many different purposes. You could use them to improve searchability (both for content teams and end-users), you could use them to set access permissions on Contentful entries, or you could use them to indicate different styling treatments (e.g., light vs dark themes) in your digital experiences. Whatever your team uses tags for, you can now manage them directly from within Compose pages.

To view and edit a page’s tags in Compose, just open the “Page details” panel, click “Manage tags”, and a list of the tags assigned to that page will appear. If you have permission to edit the page, you can assign additional tags, or remove existing ones. At this time, tags cannot be created from within the Compose interface, even if you have permissions to do so.

Because Compose offers a flattened editing interface, and most actions are handled at the page level, tags are also assigned to the page entry (i.e., the parent entry) only, and not to any child entries or references. You can still add new tags or manage tags on child entries in the web app.

Learn more about tags in our help docs and dev docs.

The Launch app helps you structure and schedule releases of content ahead of time with ease. In fact, with so much ease that it's now becoming hard to sort through the many releases being created. To bring a clearer overview, easy access to releases and to reduce clutter, we’re shipping a refreshed UI for managing releases at scale in the Launch app.

Easily access the new list view via the toggle on the top right, which offers a condensed and information rich overview of the releases. Here’s an overview of the improvements you can expect in the release management user interface;

• List view for a better overview of releases created
• Search bar for finding releases faster, by name
• Ability to archive releases, to clear up spaces without deleting releases completely
• Filter by; Publishing state (unscheduled, scheduled, published), archived releases and by users who created the release
• Sort by; Name (alphabetical), Creation date and Last updated date

The APIs that support these changes are also included in our JS SDK:

• Query parameters for Releases API that enable filtering and sorting, see documentation
• Releases Actions endpoint to query release actions in your space, see documentation

Tables are a common format for presenting information clearly. However, getting tables onto any digital property is surprisingly hard, especially in a decoupled world where a simple table is contrary to the philosophy of separating content from presentation.

To accommodate the needs of content editors and developers alike, we added tables to Contentful’s Rich Text Editor, supported by our APIs and client libraries.

With tables, editors can start organizing content, such as product size guides, pricing pages, event agendas — you name it — in a tabular form. Features include:

• Copy and paste tables
• Add rows and columns
• Enable/disable a header row
• Format text: bold, italic, underlined, code blocked, or a combination
• Add hyperlinks
• Embed inline entries

To use tables in existing Rich Text fields, you'll need to enable them in the Content model settings menu. New Rich Text fields will have tables enabled by default, but can be disabled if desired.

Learn more about Tables in the Rich Text Editor, see our developer documentation or follow this quick course on enabling and using tables.

Contentful’s Compose app is offering new and improved capabilities to maximize editorial productivity, by making it easier and faster to browse, create and publish content for any use case.

Improved page model flexibility means that Compose can be configured using any content type — with only a few clicks — using the step-by-step guide for developers and admins. Field groups make it easier to collapse fields to reduce the amount of fields in the interface, making it easier to focus on what matters. Spend less time setting up Compose to fit your needs, and more time helping teams produce content faster. What to expect:

• Easier to get started, with no development effort
• Simplified content model with less requirements and nesting
• Customizable page editor layout
• More granular validations for linking to specific page types
• From global URLs to unique URL slugs per page type
• Avoid information overload by grouping fields
• Segment content easily using tabs
• Ensure greater governance by setting up permissions to only allow editing specific page types

Learn how to install and set up page types in Compose or see our developer documentation for Compose.

Improved create-contentful-app tooling for the App Framework

The create-contentful-app CLI has been rewritten to be faster and more flexible. It is now possible to bootstrap an app with JavaScript instead of Typescript, Yarn instead of npm or even create an app from your custom template. All you need to do is run npx create-contentful-app. To learn about how to use the new features, simply run npx create-contentful-app –help. For more details, please check out our documentation.

React Hooks for building apps faster

React is the most popular framework when it comes to writing Contentful apps and with the new React Apps Toolkit, we provide multiple new React hooks that abstract the most common use cases. That way, you have to write less boilerplate code and can focus on the core functionality of your Contentful app. Combined with Contentful’s open source Forma 36 design library it allows developers to seamlessly integrate into Contentful so that you can build editorial apps faster with less manual work. To learn more about the new React Apps Toolkit, check out the package on npm.

Automation is essential when dealing with content across digital delivery pipelines, especially to help content creators and developers work together harmoniously with the tools they prefer. We are thrilled to announce the release of the new Slack app and improved Netlify app!

To date, we’ve made webhook templates available, which could be configured by any developer to trigger a notification with Slack or a build with Netlify. We now want to make this capability available for content creators too — with improved apps that are easy to install from our marketplace, rather than having to ask your developer to set it up.

With the new Slack app you can configure alerts via a message in Slack when an entry is created, deleted, published or unpublished. The messages can be customized to be richer and provide additional context.

The Netlify app is now able to trigger builds automatically, rather than manually, when content is published or unpublished.

You can install the Slack and Netlify apps via our Marketplace today! Existing installations of the Netlify app have been automatically updated.

Getting a thorough understanding of the content your teams are producing is essential for optimizing and iterating it over time. In some cases, content can be augmented with metadata to improve SEO performance or audited for gaps and enrichment.

To make the content analysis process a bit easier, we’re making it possible to download content search results via CSV export, which can be further analyzed in the BI tool of your choice. Simply run a search, configure the columns to include, select the rows to export, and click “Export as CSV” in the bulk actions menu.

When all rows are selected, the export pulls search results from the current page only, meaning that if there are more search results than on one page, you would need to export the remaining results as separate CSV files, or use our APIs.

For more information, please read our Help Center article.

We have released contentful.js v10 in Beta with enhanced TypeScript support!

With typed queries and responses, developers are able to see the shape of content types & entries right in their code editor! No more context switching, everything they need to develop efficiently is in one place.

Improvements in v10 Beta

• Query type support — Autosuggestions based on your Contentful content model allow you to know exactly which search parameters you can use in your getEntries and getEntry requests.
• Chained client modifiers — An option to modify the response shape of your getEntries or getEntry calls, and thus get predictable response type support.

Learn more

• Have a look at our tutorial demonstrating the new features
• Learn how to migrate to contentful.js v10-beta in our migration guide
• Download the new package from NPM under the beta-v10 tag (go to the "Versions" tab to find it)

Share feedback

• Submit feedback using this form
• Create a GitHub issue and tag it with the beta-v10 label
• Write to us in #general with tag #typescript on our Community Slack

Object type fields allow users to store an arbitrarily shaped JSON object within an entry. We have modified the GraphQL Delivery API to allow users filtering on whether content is set in an Object field via the _exists filter.

The Developer docs were already stating that the _exists filter is available for all field types.

You can read more about all available collection filters in our developer documentation.

On Thursday 17th at 10am CET, Contentful made an important security update to our content type field validations that use Regular Expressions. These validations live in the content type fields, for example to enforce a specific input pattern when creating or updating entries. This change will block updates to content type validations that include potentially dangerous terms, but will not prevent publication or other content type changes.

On Tuesday 17th May, we will make a further update that will prevent publication from content types that contain the potentially dangerous terms.

This change will impact customers who use certain RegEx terms to enforce formatting or validation in their content types, which will no longer be permitted. Please see below for more details on when these changes will affect different customers.

We are in the process of directly contacting Org Admins at customers who use these validations to flag which content types contain these terms this week. We cannot offer specific instructions on how to change each validation, but these communications include general guidelines to simplify the process.

Customer impacts

Community & Team customers can still edit affected content types, but only if they leave the regular expression validation untouched. From today this means that new or updated content types must comply with our new requirements for validations. Other changes to affected content types are still possible, as is publication of entries using content types.

From May 17th, all content types must comply with our new requirements. If content types are not updated to use accepted validations, it will not be possible to publish new entries with those content types. Already published content will not be affected.

Premium/Enterprise customers can still make changes to their content type validations. They have three months to make the required changes and ensure there is no disruption to their workflows in affected content types before the May 17th updates.

These updates to our regular expression engine are a proactive preventative measure against potential "ReDoS" attacks and ensure that our customers continue to have the service they expect from Contentful (you can read more about them over at OWASP.

You can now disable and enable your webhooks with a single click, giving you more flexibility in how you build with Contentful. Webhook disabling is controlled with a toggle in the webhooks settings page, and users can now easily see which webhooks are disabled.

Previously, disabling webhooks required users to delete the webhook then rebuild it from scratch. This was both time consuming and error prone, as settings had to be recreated exactly. That process is now one click to disable the webhook, and another to enable it.

Key use cases:

• Downtime: If you know the service that will receive the webhooks will be down for a certain time, you can disable the webhook to avoid having failures cluttering the webhook log.
• CI/CD: configure your webhooks and then disable them when you don't need them for testing. Re-enable them when you want to do some testing, as part of a CI/CD pipeline.
• Migrations: during migrations you may want to disable certain webhooks to not spam third-party systems. They can easily be enabled again after the migration is done, without deleting and recreating them.

Disabling webhooks is available to all Contentful customers now.

For more information on disabling webhooks, you can refer to the documentation.

We have modified the Graph API to allow users to request fields on an asset in multiple locales.

For instance, with this change you can fetch different image URLs for different languages. Previously you could only select fields in the same locale as the asset, meaning fetching data for the same asset in multiple languages required doing multiple aliased queries or multiple requests.

Here's an example:

Today we are releasing Forma 36 v4 to GA. Forma 36 is our open source design system, created to make it easy to quickly build apps and extensions for Contentful that feel like a native part of the platform.

Improvements in v4

• Accessibility - We believe that the web should be for everyone, so v4 brings Web Content Accessibility Guidelines (WCAG) level AAA compliance in all of our React components.
• Bundle size - New approach to component management uses tree shaking and loads only what you need. As a result, bundles with v4 are up to 85% smaller - making your apps faster and more responsive for end users.
• API usability - The updated Forma 36 API is simplified, follows common standards and is more consistent not only between individual components, but also with other Contentful APIs. This makes it faster than ever to build apps in Contentful.

Learn more

• How to migrate to v4 on the Forma 36 website
• Read more about the new version on our blog

Share feedback

• Create a GitHub issue with one of our issue templates
• Submit feedback using this anonymous form
• Write to us in #forma36 channel on the Contentful Community Slack

We will continue to support Forma 36 v3 until 12th July. To learn more about this, please read the maintenance plan for v3 on the Forma 36 website.

Environments Governance allows space admins to tightly control who has access to each environment, securing, simplifying and speeding up their teams’ development processes.

As our customers scale, granular access control in delivery workflows becomes increasingly important. With environments governance, admins can ensure that users only see the environments they need, letting them be much more confident in making changes, and avoid mistakes that could affect your end users.

With environments governance teams can:

• Safely share testing and staging environments with QA engineers, PMs and Editors to test and approve development changes
• Control access to the master environment, i.e. restricting developers from making changes on live content
• Protect sensitive development - allow only a few users to access a secret project or confidential data
• Train editors using realistic permissions without the risk of impacting live digital experiences
• Test new roles safely to ensure permissions are set correctly without affecting production
• Grant limited access to external contributors to only the environments that they need to complete their task.

To enable environments goverenaces, the space admin can navigate to the role editor, then environments tab and select restricted environments and aliases.

These features are available on Premium plans (or former Enterprise plans with space sizes P1X and above).

You can learn more about how to manage access to environments in our release blog, developer docs, help center, or watch the walkthrough video.

Today we released Forma 36 v4 beta, a new version of Contentful’s open source design system.

Beta means it's available to everyone, but we may still introduce some changes to the API, including small improvements and fixes. We encourage you to migrate to the new version and enjoy the improvements.

Improvements in v4

• Accessibility - We believe that the web should be for everyone, so we redesigned our React components following the WCAG level AAA guidelines.
• Bundle size - New approach to component management uses tree shaking and loads only what you need. As a result, bundles with v4 are up to 85% smaller.
• API - The updated Forma 36 API is simplified, follows common standards and is more consistent not only between individual components, but also with other Contentful APIs.

Learn more

• Learn how to migrate to v4 on the Forma 36 v4 website
• Read more about the new version on our blog

Share feedback

• Create a GitHub issue with one of our issue templates
• Submit feedback using this anonymous form
• Write to us in #forma36 on the Community Slack channel

None of your apps that use Forma 36 will be impacted with this update unless you migrate to v4 beta.

Apps now have access to Releases, Release actions and Scheduled actions making the planning and scheduling of your content even easier.

You can now build apps to manage the content and publication of your releases, or automatically synchronise releases with other tools to improve the visibility over content operations across your organization.

You can learn more in our guide on App Identities and Events.

Recently, we introduced the reference tree to the "add to release" flow for Launch. This allows content editors and orchestrators to build and schedule releases with confidence by giving them granular control over what content in their entire reference tree will be added to each release for (un)publication.

Today, we are improving how we present our filters for the reference tree in this interface, to make it easier to find the entries that are important to your release based on their state - draft, changed or published. This will help editors to build their releases more quickly by making it easier to surface the content they’re looking for.

Every schema from the GraphQL Content API contains a type named Asset which represents an asset in your space.

When querying for the asset's URL via the Asset.file field, a transform parameter can be provided to generate a URL for our Image API with all the transforms applied.

One of those transforms is format to allow altering the image's file type. We have added the value AVIF to the ImageFormat enum.

Example usage:

When applied, the resulting URL contains the query parameter fm=avif.

You can read all about the Asset type in our GraphQL developer documentation.

A picture can be worth 1,000 words, but what happens if it's worth so many bytes that your page loads too slowly? That's where AVIF image conversion steps in.

People have short attention spans so, as TUI can show you the faster a page loads, the more likely it is your users will stay and complete their purchases.

Faster page loading times will also improve your SEO performance, helping you to get in front of those customers in the first place.

To help our customers build beautiful, image-filled, digital experiences that convert clicks/views/etc into customers without sacrificing page loading time, the Image API now supports AVIF format conversion.

AVIF delivers high quality images with smaller file sizes and is fully supported by Chrome, Firefox and Android.

The image conversion happens entirely at the API level, so your content teams can continue to upload the same formats they use now, but still reap the rewards of faster load times and improved SEO rankings.

To learn more about working with images in Contentful, you can read our blog, and to start using AVIF format conversion, you can check out our Images APIdocumentation now.

On 1 November 2021 at 10:00am CET, Contentful will make an important security update to our SSO (single-sign on) configuration.

We will replace the x509 certificate that we use to sign SSO login requests with a new certificate, in order to ensure we maintain the highest level of security for our customers.

Depending on how your organization has implemented SSO for Contentful, this may require you to update configuration settings in your Identity Provider to reflect this change. If you need to make these updates and do not, you will not be able to log in after 1st November.

SSO providers that support this feature and could be affected

• Microsoft Azure AD
• miniOrange
• Ping Identity

Urgent action is required if your organization has explicitly enabled signature verification (aka fingerprint verification) for SAML authentication requests using Contentful’s current x509 certificate.

To prevent issues with SSO login, make sure to specify Contentful’s NEW x509 certificate in your Identity Provider’s Admin dashboard and reenable the verification on the 1st of November. If you would like to replace the certificate before the 1st of November 10:00am CET, contact our Support team via support@contentful.com, and we will arrange a mutually convenient time to switch you to the new certificate

If your organization has not enabled signature verification for SAML authentication requests, then there will be no impact to your service when the new certificate is activated and no action is required.

SSO Providers that are not affected by this change

• Okta
• OneLogin

If you’re unsure of how your implementation has been configured, please contact your Security or IT teams to verify.

For more information on the transition process, and to check our current certificate, please check our FAQs for SSO and for the x509 certificate update process.

We have a new release that we think is worth commenting on...

Contentful CMA (Content Management API) now includes Comments

Contentful’s Comments API, allows organizations to distribute key editorial information for their editorial teams using comments to ensure they can work quickly and avoid communications problems.

You can find more details in our developer documentation.

Contentful webhooks also now support events for Comments.

These new event topics help Contentful developers to manage automations at scale.

Webhooks can be accessed from the webhook configuration page in any Contentful space (/spaces/[space-id]/settings/webhooks).

To learn more about our new webhooks and how to use them in your content delivery workflows, feel free to visit our Help Center article.

Use cases for the new API and Webhooks include:

• Automatically add comments to a content entry from other applications, ensuring consistent information communication
• Notify digital teams when a comment is created or deleted in the apps they normally use to communicate, eg. Slack or Teams
• Trigger actions in other apps based on comments events, such as copying a comment, updating a status, etc.
• Use comments events in your app by leveraging app events

Both the API endpoint and webhooks are now avaiable to Contentful users on all tiers.

We have extended the App SDK with three new functions:

• sdk.entry.publish()
• sdk.entry.unpublish()
• sdk.entry.save()

These new functions make it much easier and faster to build apps that update the lifecycle of content (e.g. custom publish buttons, auto-save fields) by eliminating the need keep track of all fields and their IDs to publish one entry.

These improvements to the App SDK are available for all customers from today. To learn more, please refer to our documentation.

Apps can now be easily shared across organizations with a click, using a link or an embeddable share button. Apps shared using this feature will automatically receive updates.

This will make it easy for community members to share their apps with other organizations; for Contentful customers to deploy their custom apps across multiple spaces and for partners to build apps for clients.

Sharing can be enabled from the app configuration screen. Once an app is shared, a deeplink will be available on the same screen.

You can learn more about how app sharing works in the Content Management API documentation.

It is now possible to add icons to your custom apps, allowing developers to give their apps a custom look when they appear in the App List.

App icons help identify your apps and their functionality in the app list and everywhere the app definition is shown. This improves usability for organizations that use many custom apps in their environments by making it easier to quickly find the app you're looking for.

They also make life that little bit more fun!

To upload an icon, go to the app management screen and hover over the icon. When clicked, you can now upload your custom icon.

Icons introduce a new entity called AppDetails, which is used to store additional information about a Contentful app. For more information, see the Content Management API Documentation.

Apps built using the App Framework can now access the Content Management API using the official contentful-management.js client.

With release of App SDK v4, the SDKs powering our locations include a new attribute called cmaAdapter allowing developers to access entities exposed by Content Management API making using the official Content Management API JavaScript client.

This change introduces a soft deprecation of Space API, whose functionality is now fully replaced by cmaAdapter.

Learn more about this feature by visiting:

• contentful-management.js documentation
• cmaAdapter documentation
• Space API deprecation warning

Contentful webhooks now support events for tasks.

These new event topics help Contentful developers to manage automations at scale.

Key use cases for the new webhooks include:

• Communicating creation and updates on tasks to the right stakeholders in real time
• Implementing task templates
• Starting a workflow in a third party app
• Using task events in your app by leveraging app events

Webhooks can be accessed from the webhook configuration page in any Contentful space (/spaces/[space-id]/settings/webhooks).

To learn more about our new webhooks and how to use them in your content delivery workflows, feel free to visit our Help Center article.

When creating a scheduled action to (un)publish content, we used to only allow to schedule up to 2 years ahead. But then we thought, what if you need to schedule some content for the next Olympics?

To give our customers as much flexibility as possible over a longer time, we have increased the schedule time - the limit is now 5 years into the future.

This is especially useful in cases where content is relevant for a limited time, during which it can be live and which needs to be unpublished with certainty after some time in the future.

This means that if you need to schedule content for the next Scottish Parliament elections, the Winter Olympics in Milan, or the 250th anniversary of the United States Declaration of Independence, you can confidently do it with Contentful today.

You can learn more about the Schedule Actions API in our Content Management API documentation.

To our customers that use SSL pinning: From 10:00 CET on Monday October 4th 2021, our engineering team will gradual change the SSL validation chain for CMA/BE.

For more information please reach out to our support team: https://www.contentful.com/support/.

If you are not using SSL pinning then please feel free to disregard this message.

We have released major improvements to tasks in the Contentful platform, adding new features and moving them into their own app.

These new features help users to manage their content workflows at scale and ensure major projects can be delivered on time.

Before:

• Tasks could only assign a task to individual users
• Tasks were not available in Compose and Launch
• Due dates could only be added in the task description
• Tasks were a built-in feature of the web app and it was enabled by default on your sidebar

After:

• You can assign a task to an individual user or a team
• You can add a due date, which will trigger reminders two days before the due date
• You can see view urgent and pending tasks in a single location
• You can work with tasks in the Compose + Launch, as well as the web app by installing tasks from our Marketplace

Availability

Tasks are available to Enterprise customers using P1X spaces or larger - this is unchanged.

For customers who have used apps within the last 12 months, Contentful has transitioned all existing tasks to the new app in the background. For existing customers who do not use tasks and new customers, the app can be installed from our Marketplace.

Learn more by

• Watching the walkthrough video
• Reading our release blog
• Visiting our help center

Editorial flexibility is key when creating workflows and publishing content across channels, which is why we’re delighted to announce new extensibility capabilities for Compose + Launch - to editors more easily augment any workflow with apps from our marketplace or that their team has built within our dedicated experiences.

Compose

• Added support for sidebar apps.

Launch

• Added support for sidebar apps
• Added support for page apps

Sidebar apps help anyone working with content to easily augment their workflow with apps from our marketplace or that their team has built. Apps including translation management systems and DAM integrations can utilize this space to support every editors’ work in a single page.

The Page location allows apps to fill the entire page, giving developers the space to customize Launch by integrating other tools and services to the Launch’s capabilities.

You can find out more about customizing the sidebar, the specifics of sidebar in Compose and working in our developer documentation.

If you’re curious about what apps can be used in these new locations, you can learn more about building your own app with our app framework from our website and developer documentation, or see what has already been built in our marketplace.

If you love Launch as much as we do and have created a lot of releases, you may have realised that it can be tricky to find the release you're working on when adding entries and assets from the web app.

You may have said things such as "Which Release was it again?"; "Why can't I can't I find next week's sale release?" or "Why must I have to scroll through so many beautiful releases?!?".

Don't worry, help is on its way! Allow us to introduce to you to the add to release search bar! Your releases are now only a couple of keystrokes away, with the search bar filtering the list until you see only the releases you need.

Note: The search bar will only appear once you have more than five Releases in a single space. (This should be the point where you have to start scrolling through releases.)

App events and webhooks listening for entry and asset (un)publish event topics will now receive extra headers when the action was triggered by a bulk action, scheduled action, or a release.

Prior to this change, an entry or asset (un)publish event did not provide context around what triggered the action, such as a collection of entries being published by a bulk action or a scheduled release.

Users can use these new headers to apply special logic, such as delaying a build if a bulk action or release triggered the app event or webhook.

Below is an example of some of the headers that may now be sent depending on the systems involved.

Bulk action headers

• x-contentful-bulk-action-id: The sys.id of the bulk action

Scheduled action headers

• x-contentful-scheduled-action-id: The sys.id of the scheduled action that triggered the action

Release headers

• x-contentful-release-id: The sys.id of the release that was actioned
• x-contentful-release-version-id: The sys.version of the release that was used for this action
• x-contentful-release-action-id: The sys.id of the release action used

Availability

These headers are now present on all app event subscriptions and webhooks impacted by one of the above APIs. No extra action is required to include these headers.

• Learn more about App Event subscriptions in our Extensibility Guide
• Learn more about Webhooks in our Content Management API documentation

Contentful webhooks now support event topics surrounding releases, scheduled actions and bulk actions.

These new event topics help Contentful developers to manage automations at scale and build sophisticated publication automations by consolidating entry and asset webhooks into a single event.

__Key use cases for the new webhooks include:

• Release and release action webhooks will help reduce CI workflow builds by listening to a single webhook instead of listening to individual entries that are part of larger publication events. This will result in fewer rebuilds and therefore improved performance for end users if publication workflows exclusively use releases.
• Scheduled action webhooks will enable developers to catch scheduled events and automate workflows based on date and time.
• Bulk action webhooks will help developers to catch events when a batch of actions gets created and/or completed.
• Webhooks for failed release actions and scheduled actions give greater flexibility to choose where to be notified about these issues with integrations for programs such as Slack, Microsoft Teams, or Zapier.

Webhooks can be accessed from the webhook configuration page in any Contentful space (/spaces/[space-id]/settings/webhooks) and are available to all Contentful customers. Webhooks listening for specific topics will need to be explicitly opted into the new events, however webhooks listening to all event topics (*.*) will start seeing these new event types immediately.

To learn more about our new webhooks and how to use them in your content delivery workflows, you can use our documentation.

A new title[match] query operator has been added to the Releases query API, allowing users to search for releases by their given title using the same full text search semantics described in the Delivery API reference.

Full text search allows users to filter releases using a combination of phrase search and term search, where phrase search will look for an exact match of the quoted string (e.g. searching for "this phrase" will not match this other phrase) and term search will look for titles matching all of the keywords in any order.

For example, a user may have the following releases containing content for their upcoming campaigns:

• "2021-08 EU Surprise sale"
• "2021-08 SA Surprise sale"
• "2021-08 US Surprise sale"
• "2021-11 EU Cyber Monday"
• "2021-11 US Black Friday"
• "2021-11 US Cyber Monday"
• "2022-07 US Surprise Cyber Sale"

Using full text search, a user could find all relevant releases for the August surprise sale by using title[match]=2021-08 "Surprise sale"[1] , which can be read as "find all releases with a title that contains 2021-08 and also contains the exact phrase "Surprise sale".

Querying releases by title is available to all Management API users along with contentful-management.js API client users today.

Learn more about releases in the Contentful Management API reference

[1] when URI encoded this will actually look like "title%5Bmatch%5D=2021-08%20%22Surprise%20sale%22"

Default values allows users to build more consistency into their content model and helps editors to work faster by setting predefined values for fields in a content type. They are now available to all Contentful users.

Starting today, content modellers can define values for content type fields that will automatically be applied when an entry is created. This means they will be prefilled for the editor no matter if that entry is created via the Web app, Compose, the API or any of our developer tools.

• Boolean
• Plain text
• List
• Number
• Date

You are able to change the default value for a field when you create a new one or edit an existing one. Simply click on the "Default value" tab in the modal and put in your predefined value.

This video walkthrough shows how to create a new content type with default values and how to add them to existing content types.

If you want to learn more about how this can be used, head over to our help center or take a look at the developer documentation about content types.

For spaces with custom roles, the "Permissions" section of the role editor has been revamped to distinguish better between space level and environment level.

Environment-related permissions can now be found in a dedicated "Environments" tab, while space-related permissions remain in the "Permissions" tab.

See the following screenshots to see how the old and new presentation relate to each other:

Content Model and Tags

API Keys

Environment Access

Environment Aliases

Space Management

When adding content to a release, it can be important to view, select and add child references in bulk to ensure that no entries are missed for your next important launch.

Now, when you add content to a release in Launch from the entry editor in the web app, you will see the reference tree and be able to use the it to recursively select the child references that you need for your content or campaign.

To learn more about working with references in Contentful, you can explore our documentation.

Before:

Once a scheduled action had been set for an entry within your Contentful space, a reschedule would involve first deleting that action and then setting a new one for the appropriate time.

Now:

You can reschedule a Scheduled Action directly from the entry sidebar without any extra steps required!

Team and Premium/Enterprise customers will now be able to install up to 50 apps per environment (up from 10) and to create up to 250 custom apps per org (up from 10).

This will allow our customers to be much more flexible in how they extend Contentful. For example, building more utilities that allow editors to work faster, or supporting more custom integrations with third party platforms for multiple workflows.

Learn more about App Framework, integrations, and use cases in the developer documentation

Request verification requests now include new headers (x-contentful-user-id, x-contentful-space-id and x-contentful-environment-id). These provide information about which user, space and environment a request originated from. These new headers allow you to easily verify not only that a request has been initiated from Contentful, but which user and from which space and environment.

Request verification is part of the App Framework and is available for all customers. For more information about the feature, please refer to our documentation.

We have a new color system to our products.

The new color system increases vibrancy, visibility, and accessibility of important interactive elements - allowing for consistent and predictable contrast ratios across Contentful products.

We have designed a new color palette and updated the design tokens in our Forma 36 design system.

This new palette also scales better, with more and perceptually uniform hues. To support the easy migration of projects to the new tokens, we prepared a codemod.

The Scheduled Actions API now shows the error received should a scheduled action fail.

Previously Scheduled actions used to only send an email when a scheduled action failed, however there was no other way for developers to determine what the error was after execution.

The error will be exposed in the response when sys.status is failed.

An example failed ScheduledAction for an Entry:

Learn more about exposed error field in Scheduled Action Schema section of the CMA developer documentation

The character limit for space naming will extended from 30 to 64 on July 26th.

This means that admins have more flexibility when naming a space, making it easier for them to adhere to existing naming conventions within their organization. No existing spaces will be affected.

To learn more about creating a space, you can check out our help center.

We have designed a new color palette and updated the design tokens in our Forma 36 design system.

This change increases vibrancy and visibility of important interactive elements, allowing for consistent and predictable contrast ratios in the Contentful products.

This new palette also scales better, with more and perceptually uniform hues. In order to migrate projects to use new tokens, we prepared a codemod that will allow users to migrate code easily.

We will be rolling out these improvements to our products in the upcoming weeks.

Metadata is now no longer returned when it is not included in the select operator.

When fetching content using the Contentful REST APIs the select operator allows you to choose which properties you'd like to retrieve from an entity. However, since the introduction of Tags, the API always returned an extra metadata.tags property.

This was an unintentional behavior that increased the response size. We have fixed this behavior so that when the select operator is present we only return specified properties.

If you're using select operator and rely on the extra metadata.tags in the response, make sure to include metadata.tags property in the select operator value.

Read more about the select operator in the API documentation.

This change was previously announced in the API Changes log.

The CMA SDK now supports all of the available operations on the Scheduled Actions API, including creating, querying, deleting, updating, and fetching a single Scheduled Action.

Fetching a Scheduled Action:

Updating a Scheduled Action:

Canceling a Scheduled Action:

You can read more about Scheduled Actions and usage examples in our Scheduled Actions API documentation.

The Scheduled Actions API now provides the ability to update the timestamp or timezone of an existing scheduled action.

Previously scheduled actions could not be updated, meaning that developers needed to delete the existing scheduled action and then re-create it, leading to confusion and a change in scheduled action IDs. With the new API, developers can now modify the time that a scheduled action will execute without the ID of the scheduled action changing.

Updating a scheduled action follows similar behaviours to other Contentful APIs. To update a scheduled action, send the updated payload to the PUT endpoint for the scheduled action along with a X-Contentful-Version HTTP header specifying the current version of the scheduled action. The response will include the updated ScheduledAction entity, including the new sys.version for the action.

Note that the endpoint currently only allows updating the scheduledFor.datetime and the scheduledFor.timezone fields. Attempting to modify any other field will return an HTTP 400 Bad Request.

Learn more about the new endpoint, including how to use the CMA JS Library, in the CMA developer documentation

Life moves pretty fast, and sometimes you need to change your plans. That’s why we’re making it easier to change the time that a release, entry or asset is scheduled to publish or unpublish in Launch.

Old behavior: To change the scheduled time that the entry/asset/release will publish/unpublish, users had to delete the schedule and then add a new one.

New behavior: Users select “Edit Schedule”, choose a new time, then carry on with their day.

This feature is released to all Launch users today and no action is required.

Premium/Enterprise org owners and admins can now delete spaces and use that license for a new space, without contacting Contentful support. This means that it is faster for organizations to redeploy their space licenses as their content needs evolve.

This feature can be accessed from the Subscription section of the Organization settings page.

Once a space has been deleted, its license will be available to reassign from the Unused Spaces tab in the Subscription page. It can be used with a new space or to upgrade a Trial space.

If a space is deleted in error, please contact Contentful’s customer support team as quickly as possible with the details of the space affected. Deleted space recovery is only possible within 25 days.

For more information on space management, you can refer to our documentation.

The free trial of Compose + Launch for Team and Community users has been extended from 10 days to 60 days. This affects all trials active on, or beginning on, 1st July 2021.

• Current customers can activate their trial here
• New customers can create a Community Space with the Compose + Launch trial here

Visit the Compose + Launch landing page to see how they improve and accelerate the editorial experience in Contentful.

You can now host your apps using Contentful without any external hosting provider. App hosting stores and serves your app securely without any additional setup. This feature is available for all customers.

Simply head to the new “Bundles” tab when editing an App Definition and upload the build directory of your app.

App hosting also seamlessly integrates into any deployment pipeline. A new version of your app can be released with a single npm command.

To find out more read our guide about hosting apps using Contentful and how to deploy an app using create-contentful-app

Compose now supports duplicating pages. If you have cases when you need to create new pages that are very similar to an existing page you have, then this is for you.

And it also handles the entries referenced (nested) inside the page. Some referenced entries will be duplicated together with the page, while others will be linked. This is done based on whether an entry is a composition reference or not. You can tell that by whether entries are shown expanded or collapsed.

Some permissions are required for a user to see the duplicate option in Compose.

Learn more about page duplication in Compose in the Contentful help center.

To help speed up your work and make Contentful even more flexible, you are now able to choose which field is used to generate a slug.

If you ever wanted to create a slug from any short text field, not just the title of the entry, you can now make it happen easily.

While configuring a field for your content type, you can now use the appearance tab to define the field you want to use for your slug. Simply select the Slug widget, go to the Generate slug from, and select the field you want to use.

Compose now lets you customise the Page settings tab of your pages by adding references to entries and assets to the "Compose: Page" and "Compose: SEO" content types. This lets you add fields for setting a preview image for your pages or linking to a parent pages to define your content hierarchy.

Custom references to entries will be displayed as a card that you can click to edit in the web app. Learn more in our guide to extending Compose.

The CMA SDK version now supports the new Releases API.

The Releases API enables the grouping of multiple content entries for simultaneous publication, validation or unpublishing.

Releases make it easy to monitor the progress of entries and assets that are part of large events in Contentful, such as product launches, promotional events or rebranding a site, then easily publish, validate or unpublish it as a single entity.

Example:

You can read more about Releases, Release Actions and usage examples in our documentation.

The GraphQL Content API’s UNRESOLVABLE_LINK and UNEXPECTED_LINKED_CONTENT_TYPE error messages now include the ID of the entry containing the broken link. The same ID is also available in the details object under the linkingEntryId property to be used as machine-readable output for automated error handling (such as error logging).

Exposing the ID of the entry that contains the broken link in the error message will speed up your debugging process by making it much easier to identify the cause of the error.

This change is available for all customers on the Community, Team and Premium/Enterprise pricing plans.

You can read more about the GraphQL Content API in our Developer docs.

Scheduled Actions now include a sys.updatedAt timestamp as well as sys.updatedBy as a Link object, providing a more predictable location for detecting when a change has occurred on a scheduled action.

• The updatedAt field will always be a Zulu (e.g. UTC +00:00) timestamp that will be updated whenever a change has occurred, including the execution of the scheduled action.
• The updatedBy field will show the last user that made a change to the scheduled action, such as creating or canceling an action.

You can learn more about the Scheduled Actions API in the Content Management API documentation

The CMA SDK now supports the new Entry References API.

The Entry References API enables users to recursively collect references of an entry and their descendants (up to a depth of 10 levels) and returns the entry and its included references, similar to the Delivery API.

Example:

You can read more about Entry References, limitations and usage examples of other supported actions in our documentation.

You can now send the time zone information when creating new schedules in the Scheduled Actions API.

The scheduledFor.timezone property should be a valid [IANA timezone identifier].(https://en.wikipedia.org/wiki/List_of_tz_database_time_zones "Valid IANA time zones").

• Please note that the timezone is not validated against the provided UTC offset due to complexities around timezones and their interactions with UTC offsets (see https://www.w3.org/TR/timezone/ for more information around the complexities) and instead provides useful information for display purposes."

You can learn more about scheduled actions in our Content Management API documentation

The Scheduled Actions API now stores the UTC offset originally specified for create scheduled action requests, making it easier to determine the original time input by users.

Previously, the specified time sent in the request payload would be stored as a Zulu (e.g. no UTC offset) time. For example, the time "2021-05-06T11:30:00+02:00" would be stored as "2021-05-06T09:30:00.000Z" (note the hour), which is the Zulu time equivalent. Now the original value is normalized and then stored while retaining the UTC offset.

Note that this change will not have any impact on when a scheduled action is executed.

You can learn more about scheduled actions in our Content Management API documentation

App Identities can now access Task. This means that Apps equipped with an App Access Token can now read, create and update Task.

For example, publishing an entry can now be prevented programmatically by attaching a Task. In order to proceed to publication, said Task needs then to be manually or programmatically marked as done. Learn more in our guide on App Identities and Events.

We have updated the calendar page in Launch so that users can change the timezone of the content calendar.

By default, the calendar shows scheduled content in your local timezone. However, we know that it is important to be able to see what your release calendar will look like for a specific market when you are managing campaigns that are launching in different parts of the world.

We have added a globe icon to the scheduled content view so that you can quickly identify when you are viewing content in a different timezone.

With this update, users can:

• Use the dropdown in the left sidebar on the calendar page to switch between timezones
• View content on the calendar in the selected timezone

Example of globe icon on calendar to indicate selected timezone

The CMA SDK now supports the new Bulk Actions API.

The Bulk Actions API enables users to create actions that will perform asynchronously on a batch of entities on the environment level.

One of these actions is to publish multiple entries and assets:

You can read more about Bulk Actions, limitations and usage examples of other supported actions in our documentation.

We know that keeping track of product changes and improvements is important to our customers, and we’ve been working over the past few months in the quality and reliability of changelog updates (like this one!).

Today, we’re adding an update notification badge to the Contentful UI so you can easily stay up to date as we make changes. The badge is a small red dot in the top left corner of the web app, Compose, and Launch, and will appear whenever there’s a new entry in the changelog.

The same badge will appear on the “What’s new?” link in the navigation panel, and you can click on it for a quick preview of the latest updates in changelog. This way you can be aware of things that are changing and dig deeper if you’re interested, but won’t have to leave your workflow if you’re not.

We have released new features for tags in the GraphQL Content API that will help you query assets and entries across content types that share a common tag.

• The ContentfulMetadata type has been added and is accessible from the Asset type as well as from all types using the Entry interface. It can be used to select public tags associated with an entity. Read all about the new type here in our Developer docs.
• You can now query a root entryCollection field with which you can fetch entries across content types. Read more about it here in our Developer docs.
• You can also query content (entries or assets) by specific tags using the new contentfulMetadata field available in the collection filters. See all available filter fields here in our Developer docs.

For apps, we have exposed tag methods in the App SDK and made the resource accessible for backend apps. This allows you to build and customize your own workflows when using tags.

You can read more about the GraphQL API or Apps in our developer docs.

The GraphQL Content API’s DateTime scalars now returns the UTC offset (e.g. +02:00) provided from Content Management API, matching the behavior of the Content Delivery API (CDA).

Previously, GraphQL API would always return the DateTime scalars as an ISO 8601 Zulu time string, meaning a DateTime saved as "2021-04-19T09:10.000+02:00" would be returned by GraphQL API as "2021-04-19T07:10.000Z", whereas Content Delivery API would return the original UTC offset.

You can read more about the GraphQL Content API in our Developer docs.

Contentful’s SCIM integration has now been added into Ping Identity’s app catalogue with full user provisioning support. This means that user roles & permissions can now be managed directly from Ping Identity. Refer to our step-by-step configuration guide here for detailed instructions.

SCIM is available on Premium plans (and former Enterprise plans via the Scale and High Availability platforms).

• added support for the entry PATCH resource

Read more in our documentation.

Today we have released three new CMA APIs that help developers manage and publish content at scale.

• The Bulk Actions API lets you publish, unpublish or validate a large content collection in a single API call.
• The Releases API lets you schedule a large content collection to be published or unpublished in a single API call. You can also validate that the content in a release is ready for publishing with a single API call.
• The References API returns child references of the requested entry in a tree-like structure so that you can ensure that every reference is in the correct state.

By streamlining and accelerating publishing at scale, these new APIs reduce turnaround times for customers managing content programmatically and enable teams to build even more sophisticated apps for managing internal workflows.

The new APIs support both entries and assets. The Bulk Actions and Releases APIs support content collections up to 200 items. The References API returns a response up to 10 levels deep or up to 1,000 items.

The new APIs are available starting today on all current plans and space types.

Today we have launched two new apps on our platform, built to help content teams work more efficiently in Contentful.

Compose gives editors a familiar, page-based, interface to manage their web content and is much more familiar for users coming from a traditional CMS. Compose will create a new page definition within Contentful, and allow you to give your content teams a flattened interface to easily create, edit and manage the SEO of web pages.

Key Features

• Easily create and edit web pages in a flattened interface
• Publish full pages with one click
• Manage basic SEO settings and multiple locales
• Easily reuse structured content to build new pages
• Preview full pages
• Comes with a sample content model to start building faster

Launch allows teams to collaborate much more effectively and deliver faster by grouping the content for large projects into releases that can be scheduled or published as a single entity. It also adds powerful planning and collaboration tools, including a calendar view of all scheduled events in your space and workflow status labels.

Key Features

• Group content into releases for simultaneous publication
• Quickly reschedule or cancel a scheduled release
• View upcoming releases and their content in list and calendar views
• Create custom workflows states and attach them to content types

Together, they let content teams start working faster in Contentful, and deliver business critical projects more efficiently than ever.

Both apps can be installed by space or org admins from the Apps tab in Contentful, and are installed at the environment level like other apps.

They are included for all new and existing Enterprise customers, and can be added to Team plans for $1,995/month. All users can begin a 10 day trial of the apps today.

Find out more about the apps from our landing page, Compose documentation, Launch documentation or access the Learning Center courses on Compose + Launch today.

For a walkthrough of best practices for setting up the apps, join our webinar on Thursday 25th March.

With this release, we are introducing a new type of entity — tags. Tags are user-defined keywords, consisting of an editable label and a permanent ID, that can be used to create arbitrary content collections within a given environment.

The workflow for using tags requires a space admin (or other authorized roles) to create a list of tags within the space. After that, users can apply tags to individual entries/assets or bulk tag multiple entries/assets.

The use of tags streamlines content filtering and search. Content creators can use them to search across content types within the web app. Developers can effectively query arbitrary collections in the CMA and — when tags are set to be public — in the CDA/CPA.

Enterprise customers with Performance type of spaces can leverage tags further to create custom roles that allow users to restrict access, editing or publishing rights to individual content items by invoking tags. Tag-based permissions can be used temporarily, for example, while preparing an entry for publishing or permanently, as a way to accommodate multiple teams working within the same space.

Tags are supported by the Javascript SDKs, Migration libraries, and Apps SDK, with support for other client SDKs and GraphQL API coming in the near future. You can learn more about tags in our help docs or our dev docs.

This release introduces embargoed assets — a feature that restricts public access to assets based on customer requirements. When activated, the feature serves assets from a ***.secure.ctfassets.net domain, which requires incoming requests to be authenticated by attaching a dynamically generated signature before fetching the asset file.

Embargoed assets can be configured to cover only unpublished assets or all assets within the space. The feature is available to all enterprise customers and can be enabled on a per-space basis. To activate the feature please reach out to our customer support team.

Please note that while Contentful provides the necessary documentation and tooling, it is up to the customer to implement the authentication service on the client consuming Contentful data. You can learn more about embargoed assets by reading the feature overview and an implementation tutorial.

We have modified the GraphQL Delivery API to allow users filtering on the system properties of an entry or asset via comparison filters.

The firstPublishedAt, publishedAt and publishedVersion properties now support comparison filters:

• <sys property>_gt - greater than the argument value
• <sys property>_gte- greater than or equal to the argument value
• <sys property>_lt - lower than the argument value
• <sys property>_lte - lower than or equal to the argument value

The following string type filters were non-functional and have been removed from the SysFilter input type:

• firstPublishedAt_contains
• firstPublishedAt_not_contains
• publishedAt_contains
• publishedAt_not_contains
• publishedVersion_contains
• publishedVersion_not_contains

You can read more about GraphQL collection filters in our Developer docs.

We released a new package to our open source field editors that will make your life easier if you happen to develop an app that is making use of the entry editor location.

The package provides two React components that will wrap all the default fields of Contentful with its corresponding styles and structure. It will also display help text and error messages of any of the fields.

To start using it, just install @contentful/default-field-editors into your project and write a couple of lines of code as outlined in the readme. If you are looking for an example on how to do it, you can take a look at our example application for grouping fields, which takes full advantage of the default-field-editors.

More resources

• Reference documentation
• Source code and readme for @contentful/default-fields-editors
• Guides and examples on field editors

Apps using App Events can now listen for their own installation events (i.e installation, updating, and uninstallation). This allows you to perform any setup or cleanup actions required to use an app (e.g. removing data and references).

For more information please refer to our docs.

It is now possible for custom header values to include data from the original webhook payload. This was previously available for the request body but can now be achieved in headers using the same syntax. With this release customers can now integrate with services that require custom header data, increasing the number of potential integrations. Header transformations are available for all customers on v2 pricing.

For more information, please read the docs.

For spaces with custom roles, the “Content” and “Media” sections of the role editor now indicate if a rule is incomplete, i.e. if it refers to an attribute which doesn't exist anymore (e.g. a content type, an entry or an asset).

Attributes could be missing because they were either deleted or only exist in another environment.

If your roles have incomplete rules, they will be shown at the top of the list, with an indication of what is missing. They are disabled, but can be deleted.

The previous behavior was to hide incomplete policies from the web view. With the new changes, you can see outdated rules, delete them and thus keep your roles tidy.

We recently added an additional package to our open source field editors that will enable you to enrich fields used in custom apps with it's corresponding errors.

By pulling in @contentful/field-editor-validation-errors into your project you can easily render a list of the error messages of a particular field to indicate what is wrong with the input.

Resources

• Field editors source code
• Guides and examples
• Reference documentation on field editors

This face-lift brings a better representation of states and statuses and a clearer visual hierarchy of buttons. It’s the first of more upcoming updates that will introduce more consistency and less noise, both visually and in the way we structure components.

The newly released Contentful Web app is using the latest version of Forma 36 - design system from Contentful.

If you build apps and extensions using Forma 36, follow the update instructions to get the new look and feel.

We've just released @contentful/app-sdk (App SDK) on npm. This package is a renaming of the contentful-ui-extensions-sdk (UI Extensions SDK) and there are no plans to diverge the two.

The App SDK has been created to reduce the confusion caused by building apps using the UI Extensions SDK. All of our documentation and example apps have been updated to use the new App SDK for clarity.

This change does not break any apps or UI Extensions using the UI Extensions SDK. However, we do recommend using the App SDK for any new apps being built.

We have modified the GraphQL Delivery API to allow users filtering on the content in a RichText field via _contains.

Also we added the existence check, as the Developer docs were already stating that the _exist filter is available for all field types.

Example query using the functionality that has been added:

When you invite someone new to join your organization, the invitation link we send now expires after seven days. This helps us limit the possibility of someone gaining unauthorized access to your organization.

If some misses your invitation the first time around and the link expires, you can now quickly re-invite them by clicking "re-send invitation" next to their name in your organization's user list in the Contentful web app.

Find out more about inviting users to your organization in our help center article.

When searching using the query or match operator, it is now possible to search for entire phrases by wrapping the relevant part of the search query with double quotes (e.g. "this is a phrase"). The search engine will return only those results that contain exact matches to the phrase.

Phrases can be combined with each other and also with individual search terms at will. Please, find more information in the docs.

When updating an entry via the Content Management API it is now possible to send JSON patch updates via the PATCH resource.

JSON patch is a web standard format for updating a JSON document by sending a description of the changes, rather than the entire updated document. This allows developers to make substantially more granular requests for entry changesets. You may find this useful if you have a write-intensive workflows, especially when working with content-heavy documents, or where request size is a concern.

This does not affect the PUT resource and entry updates made using that resource will continue working the same as before.

When creating/updating an asset via the Content Management API it is now possible to provide an URI in the file's upload property that points to a resource exclusively served via HTTP/2.

During asset processing the file is fetched with HTTP/2 support and falls back to HTTP/1.1 if necessary.

This does not affect URIs served via HTTP/1.1 and they proceed to work as before.

This release will change the default behaviour of transformEntries. Previously, when tranformations or changes were applied to entries, the CLI published all entries after the changes were made. To avoid this, you needed to explicitly send the flag shouldPublish with the value 'preserve'.

Now with version v4.0.0, transformEntries won't publish all the changed entries, unless the flag shouldPublish is set to true. This change will prevent beginners from publishing changes by accident.

E.g Adding 'byline' property to the ContentType 'newsArticle' and publish the update

App Identities can now access Locales. This means that Apps equipped with an App Access Token can now read locales in the space-environment where they are installed. For example, knowing all the locales that an entry can be translated to and ensuring full translation coverage is now possible. Learn more in our guide on App Identities and Events to leverage our App Framework at its fullest.

Organization owners and admins can now export space resource usage to a local CSV file. The export includes the Entries and Assets usage (Entries + Assets = Records), Space ID, Created at, Created by, and the Expiry date (for Trial Spaces).

Organization owners and admins can now view space resource usage directly on the Subscription page. Alerts are displayed when Environments, Roles, Locales, Content Types, or Records usage is approaching, reached, or exceeded the limit for the space type. Help Center article

This release introduces request verification to the App Framework. Request verification enables you to verify that requests received by your app's backend have come from Contentful, and reject those that aren't.

App developers can do this by establishing a shared secret, which Contentful then uses to sign any requests coming from app events or your app frontend. The signature in these requests can then be verified in your app backend.

Now that App Definitions support both a shared signing secret and multiple key pairs, we have combined these options under the new Security tab on the app settings page in the web app.

Learn more by reading our guide on request verification or the API documentation.

Contentful’s SCIM integration has now been added into Azure’s app catalogue with full user provisioning support. This means that user roles & permissions can now be managed directly from Azure. Refer to our step-by-step configuration guide here for detailed instructions.

SCIM is available to Enterprise customers on Scale and High Availability platforms.

With this release it is now possible to read environment alias IDs using the sdk.ids namespace.

Read more in our documentation.

This release introduces instance parameters to the App Framework. Now instance parameters can be used alongside free-form installation parameters.

With instance parameters it is now possible to customize installed apps depending on their location and content type without hardcoding information in their source code.

Instance parameters for apps are on par with instance parameters for UI Extensions API-wise, but App management views in the Web App have now an advanced visual editor simplifying work with parameters while building complex apps.

App instance parameters can be used to specify default values for fields, provide shared API keys for external services, reference content types and much more.

Read more about parameters here and how they are defined within App Definitions.

We’ve updated the actions for our reference and media fields. There is now a single button for either creating new, or linking existing content or media.

We have modified the Graph API to allow users filtering on the existence of content in a Link or Array<Link> field.

The Developer docs were already stating that the _exist filter is available for all field types.

Example query using the functionality that has been added:

With the new version of the reference field editor there are two additional buttons in the card actions menu: “Move to top” and “Move to bottom”.

This change only affects the multiple entry references editor. Assets and single reference editors won’t show the new buttons.

The new “Move to top” and “Move to bottom” actions allow quickly moving references in longer lists without drag&drop. The “Move to top” button makes prepending of a newly added entry to a list more convenient.

You can check the reference editor playground to see the buttons in action.

App Identities and Events are now generally available. Apps can now function without a logged-in user or UI component, enabling numerous asynchronous workflows.

App Identities allow an app to request an access token and use it to interact with Contentful. This allows apps to call the Content Management API without using a user-scoped API key.

App Events are similar to webhooks, but are scoped to an app and the environment it's installed into. These are automatically created on app installation and removed on uninstallation, reducing any configuration time.

Try out App Identities and Events by following our new guide, where we’ll walk you through building an app that leverages these new additions to the App Framework.

Both these features are available for all customers (excluding those on legacy pricing plans).

We have modified the Graph API to allow users looking up links to an entry (linkedFrom field) in multiple locales.

With this change you can for example fetch pages that link to a specific category in multiple relevant locales, mainting the locale of your user while presenting fields content. Previously only the current selected locale was searched in. This is still the default behavior and can be overriden by the allowedLocales argument.

The Developer docs have been updated to reflect this change.

You will now be able to schedule an asset to publish or unpublish at a specific point in time. This uses the same scheduling functionality that is currently available for entries.

Learn more about scheduled publishing.

We have modified the Graph API to allow users to request the same field on an entry in multiple locales.

For instance, with this change you can fetch a slug or text preview in multiple languages. Previously you could only select a single locale for an entry, meaning fetching data for the same entry in multiple languages required doing multiple aliased queries or multiple requests.

The Developer docs have been updated to reflect this change.

We have updated the credit card purchase flow in the webapp. The flow simplifies the purchase experience and makes it clearer which space best suits your needs.

Graph API now provides a clearer error message with an error code of UNEXPECTED_LINKED_CONTENT_TYPE when an entry with an incorrect content type is linked from another entry. The error message also indicates what content type was received and the content types that are permitted.

We’ve made updates to how Enterprise customers can try more of Contentful for free. Proof of Concept spaces are now called Trial spaces and include clear communication throughout the duration of the trial. Enterprise customers still get five of these spaces.

Help Center article

Users that have opted in to the Environment Aliases feature can now create up to two additional custom Environment Aliases.

Additionally the UI has been updated to support explicitly targeting either the alias or the underlying environment, and alias update notifications are now more detailed.

Custom Environment Aliases are available to customers on the Enterprise tier.

API Documentation

Contentful’s SCIM integration has now been added into OneLogin’s app catalogue with full user provisioning support. This means that user roles & permissions can now be managed directly from OneLogin. Refer to our step-by-step configuration guide here for detailed instructions.

SCIM is available to Enterprise customers on Scale and High Availability platforms.

The reference view is a new feature to help speed up your workflow and reduce potential errors. Opening the references tab on an entry will gather every cross-linked entry and asset in a single view. This allows you to navigate quickly to deeply nested references and apply mass actions, such a publish or validate all in a single API call.

We currently can display referenced content up to 10 levels of references and display up to 200 entries and assets. The same number of entries and assets can be validated or published.

This feature is only available for customers on our Team or Enterprise pricing tiers.

Find out more at the help center article, or read our blog post.

This release allows anyone to easily introduce new editors or override the default editor for a content type. These options are now configurable in the settings of a content type.

As previously announced in the API Changes log, the time that it takes to receive an update for the auto_save webhook will decrease from 20 seconds to 5 seconds for content that has been changed in the Web App.

If you are consistently editing an entry in the web app for one minute, and you have a webhook configured to be called for auto_save events, that webhook will be called 12 times in a minute whereas previously the webhook would be called 3 times in a minute.

The Webhooks developer docs have been updated to reflect this change.

• added support for getting the current target state of an app

Read more in our documentation.

• updated our Typescript typings

We've increased the limit for pending scheduled actions per environment to 500 actions. You can have up to 200 entries scheduled to be executed in a single minute. See more in the content management API reference guide.