Save status

See exactly when your work is saved—and when it isn’t.

• The Save button highlights when changes need saving and shows a spinner while saving is in progress.
• You’ll know when it’s safe to navigate away.
• Pro tip: press Ctrl/Cmd+S to save (and Ctrl/Cmd+Shift+P to publish, if available)

Combined locale & edition menu

Manage content variations in one place.

• Locales and editions now live in a single, unified dropdown.
• It’s clearer which locales exist for each edition so switching between editions no longer interrupts your flow with extra pop-ups.
• Reminder: Editions are available for projects on an Enterprise plan

Project map and dynamic preview values

Dynamic preview values are easier to access and update

• Dynamic inputs are now co-located with the project map path, keeping related settings together.
• Click a project map segment to edit its preview value directly or use nearby controls to adjust query strings and quirks.
• Preview values apply instantly through a lighter, more intuitive interface.
• You can still edit an attached project map node using the project map icon.

Component internal names

Add meaningful internal names for clarity and collaboration.

• Give each component instance an internal name to identify its purpose.
• Internal names override “display name” parameters.
• Use this to make a shorter name or identify the intent of sections (e.g. “Rotating promotional section”).
• This is an internal-use-only name and will be stripped by our edge delivery API so it is not included in the front-end payload.
• Hover over the name field for an AI edit tool to provide some inspiration based on the component’s content.

Internal test hypothesis

Keep your team aligned on the “why” behind each experiment.

• Add an internal hypothesis for A/B tests and personalizations.
• These notes can help clarify what’s being tested and why.
• These are stripped by our edge delivery API and is not included in the front-end payload.
• Scout AI is aware of hypothesis fields and will read and write to them, using them to guide content creation.

Smaller changes

• Unpublished content mode: This toggle now lives exclusively in the data resources panel. As a shortcut, Alt + Click or Option + Click the data resource side rail icon to quickly toggle on and off. When enabled, the icon updates to remind you that unpublished content is included.
• Hidden parameter controls: Status and action icon buttons for parameters are tucked away until the parameter is hovered or activated, helping reduce clutter and increase focus.
• Required indicators: Required parameters and pattern data resources now display an asterisk (*).
• Workflow status: The Save button menu now shows workflow status, publish status, and last-published date.
• Open button visibility: Improved styling for the “Open…” button in the global nav makes switching compositions or entries faster.
• Editor polish: Slimmer side rail, refined borders, and visual tweaks give the editor more room for you to work in.
• Bug fixes and performance: Various design, stability, and system improvements across Uniform.

Renaming Patterns to Component Patterns: To avoid any confusion with our latest addition, Entry patterns, we've updated the terminology. What were formerly known as "Patterns" are now referred to as "Component Patterns".

Visual Enhancements: We've revamped how Component Patterns are presented in Uniform's visual workspace. Now, you'll notice:

• Clear identification: Special indicators in the structure panel and component highlighter make instances of Component Patterns easy to spot, enabling you to take pattern-specific actions with ease.
• Fresh Icons: We've introduced new icons for both Component Patterns and Entry Patterns

Enhanced discovery and management of Component Patterns: Introducing the Component Pattern Library, your centralized hub for effortlessly accessing and visually exploring all Component Patterns within your project.

Documentation Revamp: Alongside these changes, we've overhauled our Pattern documentation. Now, it delves deeper into various aspects such as use cases, pattern overrides, and best practices, empowering you to leverage Component patterns to their fullest potential.

Here's what's new:

• Flexible and fast content discovery: Finding and managing entries just got easier and faster. Our improved search, filtering, and sorting options help you locate and manage entries with speed and precision.
• Powerful search, filter and sorting capabilities: You can now filter entries based on custom fields, entry metadata, and conduct full-text searches. A wide range of search operators make it easy to find exactly the content you need. Also we expanded the range of sorting options that are available.
• Intuitive search interface: Our redesigned search UI offers greater flexibility, making it a breeze to build complex search queries using multiple conditions and combining it with full text search with full control on sorting.
• Improved listing of entries: Select from three different list view modes (List, Large List, Grid) to tailor your browsing experience according to your preferences. Choose from text-only compact lists to visually engaging card views presented in a grid format for your entries.
• Filter by locales: Keep tabs on localization status of entries. Now you can quickly identify translated content and track missing translations, simplifying your localization management.
• Enhanced querying flexibility: Seamlessly integrate entries into various contexts with enhanced querying capabilities. Whether you're consuming entries with compositions or component patterns, or leveraging Uniform APIs or Canvas SDK, you now have more flexibility to discover and query entries than ever before.

Architects can manage prompts for authors to use when creating compositions and content entries.

The first integrations include OpenAI, Writer, and OctoAI Stable Diffusion. You can also bring any custom model or service into Uniform with new Mesh extensions.

Learn more about how this technology helps marketers scale their experiences.

Conditional logic can be applied on two different levels:

• On a component level using Component visibility control
• On a property level using Conditional values

Component visibility control

Dynamically control which components to show or hide based on specific conditions.

Conditional Values

Adjust content and layout in using data from external systems, dynamic URLs, or frontend quirks such as device and session data. This flexibility allows marketers to fine-tune the user experience for each visitor. This feature requires an enterprise plan.

For more details on how to get started, visit the full documentation.

Once enabled, this new mode allows for selecting either changed or newly created unpublished content from a supported integration. This enables previewing experiences without the need to publish external content.

There are three content sources supported now, with more integration support coming in the near future.

• Entries from our own CMS, Uniform Content. This mode can be switched on by switching a toggle.
• Entries from Contentful, where you can now use either Preview API or another environment when the unpublished mode is active.
• Generic HTTP Request integration that now offers two independent sets of parameters.

• Reusable compositions: Build complete compositions, pre-connect them to data, and make them available as patterns for editors to use with new compositions in a templated way. This is ideal for data-heavy and complex compositions like product detail or article pages.
• Editorial flexibility with some guardrails: On compositions that are instances of a composition pattern, you can allow editors to override data resources, specific parameters of components that were defined in the pattern. Editors can also enrich compositions with additional components by configuring slot sections in the pattern.
• Centralized updates: By updating the composition pattern, you can promote changes to all composition instances of the pattern with a single click.

With composition patterns, you can define the right amount of editorial flexibility to empower your content team while ensuring consistency, simplicity, and efficiency and simplified maintenance.

To get started with composition patterns in your project please check our documentation or watch this video.

The unpublished content mode for Contentstack offers two flexible strategies:

1. Preview unpublished content - Use Contentstack's Management API to work with draft entries from the same environment
2. Separate environment - Work with published content from a different environment, ideal for staging workflows

To enable this feature, simply check the "Enable unpublished mode" toggle when configuring your Contentstack data source and select your preferred strategy.

Learn more about configuring unpublished content mode for Contentstack in our documentation.

• Repurpose existing components: You no longer have to build a component from scratch. Instead, copy an existing component that fits your needs, paste it into your composition, and adjust it as necessary.
• Paste anywhere: Seamlessly copy and paste components within a composition or across different compositions.
• Cross-project compatibility: Copy and paste components across Uniform projects sharing the same set of components and component patterns, enhancing consistency and productivity in multi-project environments.

Consult the documentation to learn how to start copying and pasting components.

This feature is designed to address the complex needs of global, multi-market content strategies and adapting to seasonal or campaign-specific content requirements.

Key benefits and use cases include:

• Market-specific content: Tailor content structure and workflow for different regions or markets.
• Campaign management: Create temporary versions for seasonal promotions or campaigns.
• Independent publishing: Manage separate content lifecycles for each edition.
• Flexible activation: Apply editions selectively to specific compositions or entries as needed.

Refer to our documentation to learn more about editions.

The Editions feature requires a Uniform Enterprise plan. Please contact your Uniform representative to provision your project with this feature.

New editor controls

In addition to the default controls, the following options are now available for the following parameter and field types:

• Single-select — Radio buttons, segmented control (text, icon and text, or icon only), or slider.
• Multi-select — Checkboxes for full visibility of all options.
• Number — Slider with optional steps for bounded ranges.
• Boolean — Switch with a custom label, or segmented control with custom labels (e.g. No/Yes).

All new controls support common features like localization and conditional values. Choose the editor that best fits each parameter or field under Editor settings.

Clear any value with one click

Every parameter and field now also includes a Clear current value option in its dropdown menu, letting authors reset any value with a single click.

Learn more in the parameters documentation.

Imagine the power of a multi-source content model built visually, allowing you to connect any number of content sources within a single model. For example, a complex Product model built composable can draw content from many content sources—product meta-data, images, pricing, availability, and recommendations—all coming from different sources.

Entry patterns, is our latest new CMS capability that simplifies this complexity for marketers, merchandisers, and developers, allowing them to create a new entry from multiple sources in a couple of clicks.

To learn more about entry patterns please check out our documentation.

Entry previews

{% vimeo videoId="1092529196" caption="Preview a blog post entry in different compositions" /%}

Entry previews let you see how your entries will actually look in different compositions before you publish them. No more guessing whether that blog post title will work on both the homepage and the detail page. Configure the entry preview at the content type level, then hit the Preview button when editing an entry to see it rendered in context.

Nested entry editing

{% vimeo videoId="1092458783" caption="Nested editing of entries from a composition" /%}

Nested entry editing means you can edit related entries without losing your place. Whether you're working with data resources in compositions or reference fields in entries, you can open a nested editor that overlays your current screen instead of navigating away.

These features work particularly well together. Preview an entry, spot something that needs fixing in a related entry, edit it without leaving the preview, and see the changes immediately.

Both features are available now for all projects. Check out the documentation for entry previews and nested editing to get started.

To address these issues, two highly anticipated enhancements have been added to dynamic tokens:

Error Handling: This feature helps manage the impact of missing data for a dynamic token on page rendering. It also allows setting an error level for the Canvas editor and API. Moreover, you can delete an optional dynamic token within a parameter, remove the entire parameter value or component, or set a fallback default value if data is missing. If crucial data from external sources cannot be resolved, you can return a "Page not Found - 404" error. This feature simplifies, or may even eliminate, the need for error handling in dynamic pages or similar scenarios in your application code.

Path Editor: This feature facilitates the manual editing of the path to a data element in a dynamic token. It is particularly useful when setting up a loop component or dynamic composition where the data resource doesn't contain all the required data elements for placing dynamic tokens. In such a case, you can manually set the desired path even if the value is not present in the current data resource.

To get started, please refer to our documentation.

What's new

EU region in Frankfurt, Germany
New Uniform teams can now be created in our EU region (eu-central-1), with all data stored in Frankfurt, Germany. The US region (us-east-1) in Virginia remains available as the default option.

Why this matters

• Meet compliance requirements – Keep your data in the EU to support GDPR and other European regulations
• Data residency control – Choose the region that aligns with your organizational policies
• Stay close to your users – Manage content in the region nearest to your European audience

What's stored in the EU region

When you choose the EU region, all your Uniform data stays in the EU:

• Projects and content
• Team member information
• Account data

How to get started

Contact your Uniform account representative or reach out to support to set up a new team in the EU region.

Once your team is created, you'll need to configure your SDK and CLI to connect to EU endpoints. See the regions documentation for setup instructions.

Learn more about regions

You can now also manage and work with these additional media types:

• Audio files (.mp3, .wav, .ogg, .flac)
• Video files (.mp4, .webm, .ogg)
• Documents (.pdf)
• Data files (.json, .zip, .lottie)

Additionally, we’ve introduced a new validation rule for Asset parameters and fields to restrict the allowed media type.

Increased file size for assets

To support these new formats, we’ve increased the maximum file size per asset from 10 MB to 50 MB.

Getting started

To use the new media formats in existing asset parameters or fields you need to enable these in the validation settings of your component or content type.

Learn more about the asset library in our documentation.

What you can do:

• Browse and preview Frontify assets within Uniform's asset library
• Select Frontify assets for use in asset parameters
• Access Frontify metadata for selected assets

Learn how to set up the Frontify integration

Key benefits

• Define query strings once and use them across all nodes
• Use in component and composition patterns for conditional logic and data resources
• Ensure consistent naming conventions, default values, and allowed options

Predefined options for query strings

Query strings now support predefined options with dropdown menus that present authors with allowed values when previewing, reducing errors and ensuring valid parameter values.

Getting started

Configure global query strings in Settings > Project Map under Global Allowed Query Strings. Learn more about configuring global query strings, using query strings as dynamic inputs, and leveraging them in patterns.

Visual refresh

We’ve given Uniform a modest refresh: making panels softer, normalizing drop shadows, and adjusting fonts. In addition to accommodating the global navigation changes, this also helps increase the visual cohesion between the Canvas editor and other areas of the application while modernizing our overall application feel.

Global Navigation

The Canvas editor is central to building experiences and managing content in Uniform. With this release, it is now visually integrated with the rest of Uniform. In the new global navigation, you’ll always be able to tell which project you’re working in and have quick access to anywhere or anything else.

In the main menu, we’ve highlighted the three core objects marketers work with daily: entries, compositions, and assets. Compositions and project map go hand-in-hand, so you’ll find them both under “Compositions” and we’ll save the view you used last, so you always return to compositions in the same view.

Speaking of accessing compositions, the “open” button inside the Canvas editor has become more prominent in the global navigation. If you haven’t tried this feature yet, it lets you, for example, jump from one composition to another.

We’ve seen many of our users — especially during the architecture phase of a project — needing to constantly switch between a small handful of different items leading to lots of clicking between lists or trying to maintain open tabs. Now, a list of your recently opened items are available from anywhere via the “Recently viewed” menu next to your avatar.

Sidebar filters

For many listings, such as compositions and entries, the sidebar contains links to one-click apply common filters. Quickly filter by publish status on the composition listing, content type on the entry listing, category on components, and so much more.

Project map editing

You can now edit project map nodes directly in Canvas now! Clicking on the project map node chip allows you to edit the node or move it within the project map. At the same time, we’ve made it a little more difficult to accidentally change which node the composition is attached to.

This is one more step in helping you keep a composition open while being able to edit other, related, items; we’ve got exciting updates coming on that front, stay tuned!

This update allows hiding the parameters that are not overridable by default, therefore reducing the amount of visually rendered parameters on a Component Pattern instance, improving the usability when working with complex Component Patterns.

Any previously uploaded images used in Image URL parameters will continue to function normally, but you cannot upload new images through this method.

For all image upload needs, please use the Asset parameter, which provides improved asset management capabilities.

If you have any questions about this change please contact the Uniform support.

Customers told us they wanted more flexibility, like overriding localization on a per-instance basis. For example, they wanted to use a single dynamic token to supply localized data, rather than repeating that same token for each locale.

Now parameters and fields marked as "Localizable" may be localized.

Architects can set a default, but editors can override this setting in Canvas for each component or entry instance. Fields and parameters that are not localizable will continue to not have locale-specific values. Existing fields and parameters marked as localizable will be set to “localized”.

Additionally we are introducing a new "Locale values" drawer that provides an overview of all localized values of a property without having to switch locales.

With this feature, along with other recent and upcoming localization enhancements, editors now have more control to avoid tedious repetition when managing localized entries and compositions.

Learn more about how to manage locale-specific values in our localization guide.

Multiple preview URLs per project

Switching between different environments is now easier than ever! With the ability to configure multiple preview URLs, you can quickly toggle between development, staging, and production previews without affecting other users. This makes it simpler to test how content looks in different deployment environments, speeding up the development and content review process.

Configurable preview viewports

You can now define up to three custom preview viewport sizes for your projects. This allows you to tailor the screen sizes to match your project's target devices, helping editors optimize content for responsive behavior across various screen sizes and platforms.

Added CLI support for preview settings

If preview settings should be shared across multiple projects then you can use the CLI to sync preview URLs and preview viewports.

Requires CLI version >= 19.201.1

Improved Project Settings Navigation

To simplify navigation, we’ve reorganized the project settings interface. Previously, the project map, localization, and preview settings were all bundled on a single "Canvas settings" page, which could be overwhelming. Now, these configuration pages have been separated into a clear and intuitive sub-navigation, making it easier to access and manage specific settings.

You can get a overview of these improvements by watching the introduction video or by checking out the updated documentation..

When you have access to more than 5 projects, a new search box will appear in the project selector, allowing you to search for projects by project or team name. Using the project search will make it easier to find the right project to switch to.

Former location in main nav

New location in Settings

Today, we launched with the first two agents - @Scout and @Sage, each specializing in their respective areas - @Scout in experience optimization and @Sage in SEO.

These agents work 24/7 to boost your team’s productivity and can take actions on your behalf—from launching an A/B test or personalization with optimized content to helping you understand key insights while consulting our Uniform Insights layer for data.

This capability is available now as an add-on for our Enterprise tier customers. Please contact your Uniform representative to provision your project with this feature.

Grouping and tagging of locales

When working with many locales for specific markets or regions it can be very time consuming to apply the right changes for each region and language while keeping a good overview. Our new locale management enhancements allow you to group locales to represent a market or region, making it easier to work with larger sets of locales.

Additionally, you'll have the option to tag related locales for bulk actions, like sharing translations across all locales using the same language or to localize content for a specific region.

Bulk selection and actions across locales

Both locale groups and tags can be used to perform various bulk operations such as:

• Enable multiple locales simultaneously for a composition or entry
• Copy translations across multiple locales by group or tag. This action can be applied at different levels of detail: for a single parameter, a single component, a tree of components, or the entire composition.
• Simplified bulk selection of locales by group or tag for entry search

Learn more on how to localize across different markets in our latest recipe.

• manage as many locales for your projects as you need
• Define localizable parameters for components and content types
• Seamlessly translate compositions and entries across multiple locales
• Adapt your compositions to market-specific needs with Structural Localization
• Utilize the innovative "Locale" project map node for locale-aware routing and linking
• Fetch localized content and data effortlessly from third party systems with Mesh integrations supporting Contentful, Contentstack, Sitecore, Kontent.ai, Commercetools, and more to come!
• Locale mapping for Mesh data sources

Check out the Localization documentation to get started.

With this release you are now able to localize project map nodes to generate locale-specific URLs to better serve different language regions, improving search engine optimization and user experience.

Learn more about this feature in our documentation.

New location types

Project tools

{% vimeo videoId="1103409876" caption="Example of using the Project Tools location to embed a full-page Storybook" /%}

Add custom tools at the project level that appear in the main project navigation. Perfect for embedding analytics tools, content importers, or project documentation such as Storybook references.

Dashboard tools

{% vimeo videoId="1103409915" caption="Example of using the Dashboard Tools location to embed a custom editorial dashboard" /%}

Extend the main Uniform dashboard with custom tools that appear alongside existing workspace features. Ideal for content filters, editorial dashboards, or training resources.

Editor tools

Add custom tools directly within Canvas editors for compositions, component patterns, entries, and entry patterns. These tools appear in the left sidebar of the editor, enabling utilities such as AI translation or content validation.

Getting started

These new location types are available with the latest Mesh SDK versions. For detailed implementation guidance, see the custom Mesh integration guide and Mesh locations documentation.

• Sub-navigation is changed to a grouped mega menu
• Content main nav item will be renamed to Experience
• Optimization: will now have deep links into Context entities like Signal, Audiences, Quirks, …
• Integrations: no changes
• Settings: added sub navigation for quicker access to  project and Canvas settings

Shipped 19.78.0 platform and packages

Meet Scout: Uniform's AI agent

Scout is your all-in-one AI assistant built into Uniform. Scout began as a site optimization specialist, but has evolved into a complete digital experience assistant. It now combines everything from the original Scout and Sage agents into one powerful tool.

Scout's key capabilities include:

• Content creation and editing: Create new compositions and entries through natural conversation. Edit existing content, add components to slots, and manage content relationships.
• Personalization and A/B testing: Set up personalized experiences with intelligent audience suggestions, configure A/B tests and variations, and declare test winners.
• SEO optimization: Generate SEO reports, automatically fix issues, update meta tags, and get SEO-friendly content suggestions.
• Accessibility and performance: Receive accessibility improvements and performance recommendations for your pages.
• Localization: Enable or disable locales and translate content between languages while maintaining context and tone.
• Platform guidance: Get answers about Uniform concepts, features, and best practices.

Scout is now globally accessible throughout the platform from the navigation bar, making it available wherever you're working. Scout remembers your context as you work and lets you organize multiple tasks in different conversations.

AI guidance

AI guidance teaches AI your brand voice and content requirements through a three-level system:

• Project level: Define company-wide voice, tone, and editorial conventions
• Component and content type level: Set contextual purpose and usage guidelines
• Parameter and field level: Specify exact requirements for individual fields

This layered approach ensures AI-generated content automatically aligns with your brand guidelines, resulting in consistent, on-brand content that needs minimal revision.

AI quick edits

AI quick edits deliver instant, context-aware updates to individual fields. Simply enter a prompt—such as "make this more concise" or "translate to Spanish"—and the AI updates the field immediately.

Quick edits help you:

• Iterate quickly on messaging and copy
• Translate content while keeping context
• Save time on repetitive updates

All quick edits follow your brand guidelines through AI guidance.

Uniform MCP Server

The Uniform MCP Server brings Uniform capabilities into AI-assisted applications like Cursor, Claude, Windsurf, and other MCP-compatible tools. Now in General Availability, the MCP Server lets developers and experience architects work with Uniform directly from their preferred AI tools.

With the MCP Server, you can:

• Create and manage components, content types, and patterns using natural language
• Build compositions and entries without switching to the Uniform UI
• Enable seamless workflows where ideation in external tools flows directly into Uniform with proper structure

This integration dramatically accelerates development velocity and reduces context switching.

How to get started

All AI features require AI credits, which are allocated monthly based on your team's subscription.

Learn more about Uniform's new AI capabilities in our documentation.

Uniform already included parameter- and field- level translation capabilities, and with this integration you can perform translation on a complete composition or entry right within the visual experience editor.

Learn more how to add this integration to your project and how to use it in our docs.

Learn more how to install and use this integration in our docs.

• Save time: Streamline and automate your translation workflows, reducing manual efforts and accelerating your content delivery.
• Enhanced workflows: Integrate translation seamlessly into your existing processes, including review and approval stages, for a more efficient workflow.
• Improved quality: Ensure top-notch translations by leveraging professional translators and advanced AI technology

Introducing Smartling TMS integration

Smartling is our first integration under the TMS category, and it offers a lot of benefits:

• Comprehensive management: Efficiently manage translation projects with Smartling’s robust tools, ensuring accurate and timely translations.
• Seamless integration: Easily incorporate translation tasks into your workflows, maintaining high standards with options for review and approval.

To learn more about setting up and using the Smartling integration, check out our documentation and tutorials.

Date with Time

Allows you to set a date and time in a specific timezone for supporting global content that respects daylight saving times (DST).
Example use cases: Start and end date of an event or promotion or the publish date of an news article.

Multi Select

Lets a user select multiple values from a list of options that are assigned to the parameter.
Example use cases: simple tagging or categorization of articles or assigning multiple options to a product

Note: as part of this release the parameter type "Dropdown list" was renamed to "Single Select". This is purely a naming change and doesn't require any customer actions.

Improved personalization capabilities

Simplified personalization

Our personalization engine now offers more flexibility in how content variations are selected for your visitors. Beyond our existing "Top-down criteria matching" selection method that supports advanced personalization requirements, the new "Strongest variation matching" selection method significantly simplifies personalization setup.

This intuitive approach:

• Focuses on a single dimension per variation rather than complex criteria rules
• Automatically selects the variation matching the visitor's strongest dimension score
• Removes the need for manual ordering of variations
• Makes personalization more accessible for marketing teams

Best for: Straightforward personalization scenarios where you want to match visitors to clear audience segments or interest categories.

Custom personalization logic

For those requiring custom personalization logic, we've added support for creating your own selection methods through our Mesh framework. This powerful extensibility capability lets you:

• Implement bespoke algorithms tailored to your specific business requirements
• Create personalization rules based on external data sources
• Define custom variation selection logic that integrates with your existing systems
• Gain full control over how variations are configured and selected

Best for: Advanced personalization needs that go beyond standard selection methods.

Nested personalization

We've also introduced nested personalization, allowing you to place personalization components within other personalization components. This creates sophisticated decision trees perfect for hierarchical targeting needs.

With nested personalization, you can:

• Create multi-level targeting scenarios (e.g., region → city, industry → company size)
• Combine different selection methods at each level
• Build complex personalization experiences without developer intervention

Best for: Multi-dimensional personalization needs that require hierarchical decision-making.

Enrichment tagging for entries and components

The new Enrichment parameter type for both components and content types brings enhanced flexibility to how you classify visitors based on the content they interact with. This parameter is especially valuable when used in dynamic compositions (such as detail pages for articles or products) where enrichment values need to vary based on the specific content being displayed.

The "Enrichment tag" parameter on components can now be connected to data resources, allowing you to dynamically assign enrichment values based on your content. This creates a more accurate visitor profile based on actual content engagement rather than static values.

We've also made various UI improvements to how enrichments are assigned.

Best for: Dynamic websites with content-driven personalization needs.

Quirks as direct personalization criteria

Finally, you can now use quirks directly as criteria for personalization variations without first wrapping them in signals. This streamlines your personalization setup when working with:

• External systems (such as a CDP or CRM)
• Application context (such as geo-location or user login status)
• Boolean or attribute-based personalization scenarios

Best for: Personalization based on visitor attributes or external data rather than behavioral scores.

Getting started

To leverage these new capabilities, update your Context SDK to version 20.9.0 or higher and explore our updated documentation for detailed implementation guidance:

• Personalization guide
• Enrichments guide

This integration allows content authors to drastically simplify and fully automate translations of compositions and content entries from the Uniform visual workspace.

Learn more how to install and use this integration in our docs.

Previous Sanity integration is now deprecated and it is to be removed on December 1st, 2024

Image Delivery API

We’re introducing the Image Delivery API, a new service for delivering image assets managed in the Uniform Asset Library. Images are automatically optimized and delivered via a global CDN, helping reduce page weight and speed up load times across devices.

Key benefits include:

• Automatic selection of the most efficient image format (AVIF, WebP, or original) based on browser support
• Real-time image resizing and transformations using query parameters
• Cropping that respects focal point settings for better subject visibility

Developers can use the imageFrom utility from the @uniformdev/assets SDK to programmatically apply transformations and generate optimized image URLs.

Learn more about this new API in our documentation.

Image Focal Point Support

Content editors can now visually define a focal point on image assets directly within the Asset Library. This focal point ensures that the most important part of an image remains visible when the image is cropped.

• Drag-and-drop UI to set the focal point
• Preview mode to simulate how images will crop across various aspect ratios
• Override the default focal point per usage within components to tailor cropping behavior for specific contexts

Learn how to set focal points for better cropping results in the focal point documentation.

Example: When using a "Featured Product Hero" component within a "Landing Page" pattern, you can now specify different products for each Landing Page instance, rather than being limited to the product defined in the original pattern.

With this new pattern usage tracking, you can now;

• Check at a glance which patterns are currently being used within a project and to what extent,
• and, users will be able to dive deep into usages to identify instances of patterns within compositions and entries.

Two key features will help teams better coordinate their work:

First, real-time presence indicators will show you which team members are currently editing the same content. You'll also be notified when opening compositions or entries that others are actively working on.

Second, intelligent conflict detection will protect against accidental overwrites. When attempting to save, you'll be alerted if another user has saved changes while you were editing. You'll be able to review the differences and see who made the most recent changes before deciding how to proceed.

Refer to our documentation to learn more about these new features.

From today, our preview panel will allow you to switch between two modes, depending on how you want to interact with your preview;

• Editing mode - enables visual editing and inline editing, helping users to quickly update content and manipulate components from within preview panel.
• Preview mode – removes the Uniform editing UI from the preview panel and enables page interactions in order to provide a clean preview experince for reviews and testing.

For more information, check out our documentation.

With project policies, you can configure permissions per role, per project, covering all aspects of the Uniform platform from content management to experience modeling and optimization. This enables you to create custom access control patterns that match your team's workflow and security requirements.

Granular targeting

For compositions, entries, and patterns, project policies support granular targeting criteria:

• By type: Target all entities of a specific composition type, content type, or component type
• By pattern: Target entities that match a specific composition pattern, component pattern, or entry pattern
• Specific entities: Target individual compositions, entries, or patterns by selecting them directly

This granular targeting enables use cases like restricting editors to only specific content types, enforcing creation of compositions based on composition patterns instead of allowing free-form creation, restricting who can manage patterns, or protecting critical content from unauthorized changes.

CLI support

Project policies can be managed programmatically using the Uniform CLI. The policy-documents commands allow you to pull, push, and sync policy documents across projects, making it easy to maintain consistent permissions across development, staging, and production environments.

Getting started

• For comprehensive guidance on project policies, see the project policies documentation.
• To understand how project policies fit into Uniform's broader access control system, see the roles and permissions guide.
• For some examples of common permission configurations, see the common scenarios guide.
• To manage policies programmatically, see the policy documents CLI commands documentation.

Key improvements:

• Quick content access - New quick access buttons provide instant navigation to manage compositions, entries, and assets from the dashboard
• Recent work visibility - "My recents" section shows your recently modified items with timestamps, making it easy to pick up where you left off
• Embedded project map - Direct access to your project map structure without leaving the dashboard
• Release planning - New releases section displays upcoming releases with dates and item counts
• Quick create shortcuts - Fast-track content creation with one-click access to create compositions, components, signals, and tests
• Product updates - Stay informed with the latest Uniform product releases and access the changelog directly from your dashboard

One of the main powers of structured content is the ability to break it down into reusable content items and express relationships between them, such as the author of a blog post, the category of a product, or the sponsor of an event. Defining these relationships allows content to be assembled and queried flexibly while avoiding duplication and reducing the risk of showing outdated content.

With the new Reference field you can setup single or multiple content references between entries. Validations can be configured to restrict references to a set of allowed content types and to define a minimum or maximum number of references. To query and resolve deeply nested entries you can either do it in a visual way using data resources in our visual editor or in a coded way using Uniform’s APIs and SDKs.

• Preview apps can signal an auth/setup interstitial so contextual editing waits instead of failing within Canvas (UNI-9053)
• Next.js page and app router SDKs now support releases in preview mode (UNI-9100, UNI-9102, UNI-9119)

Bug fixes

• Fix an issue whereby users with read-only access to edit project map node settings, loop settings, AB tests and pattern data (UNI-7127)
• Fix a zero result loading state when searching for compositions on a slow connection (UNI-9079)

Uniform packages published with version 20.58.0

• A new package 19.135.0 was released with no breaking changes

Bug fixes and improvements

• Preview of protocol-relative assets: Fixed an issue where image URLs without a specified protocol (http, https) wouldn’t display correctly. Now, all images will preview properly regardless of how the URL is formatted.
• Project Map package: improved the deserialization logic of project map nodes to make it more future-proof.

• Fixed timestamp type on manifest publish webhook schema, preventing manifest cache clearing from happening after manifest:published webhook is fired.
• Fixed validation of null values on dynamic tokens
• Fixed changing of error handling settings for data binding
• Now signals and quirks can have same IDs, before it would cause errors
• Fixed filtering by reference field

Improvements

• Binding in loops has improved error handling
• New diagnostic mode for API calls - no-data. Use this if you want to skip data resource values while keeping metrics.

Deprecations

• GA4 (Google Analytics) integration has been deprecated and, therefore, disabled.
  Due to GA4's limited Reporting API capabilities, the integration had very little value within the Uniform project. This change has no functional impact on the Uniform tracker functionality, and the GA4 tracker plugin will continue functioning as is. We recommend using GA4 dashboards directly to analyze personalization performance and A/B test effectiveness. Consider using Uniform Insights to get integrated analytics right within Uniform Canvas. Contact us for more details.

Package update

• Uniform packages published with version 20.13.0.

• A new package 19.136.0 was released with no breaking changes

Bug fixes

• Project Map: Fixed an issue where deleting a project map node previously attached to a now-deleted composition would show an error to the user.

• Resolved an issue that affected dynamic token visibility criteria that used the "is empty" or "is not empty" operators
• UNI-7113 Fixed the issue where draft composition could be accessed outside of the Next.js draft mode (Next.js App Router SDK.

• Fixed an issue where previous usage tracking bug fixes were not being applied to certain projects, we re-indexed usage data for those projects (UNI-9187)

Uniform packages published with version 20.60.0

• Fixed issues editing description and thumbnail URL of patterns (UNI-6049).

Improvements

• Project list on the team page is now sorted based on created date for consistency with other project list functionality (UNI-7236).

• CLI: improved telemetry

Bug fixes:

• Dashboard: Show Block type thumbnail if available UNI-4967

Uniform packages published with version 20.60.1

• Now it is possible to use "contains" criteria when creating Context Signal based on Quirks of "List Data" type.
• no results component to data resource query results viewer 

Bug fixes

• Regex validation on multiline text parameters now executes with a multiline flag.
• Fix tooltip descriptions for sort options in SortItems component
• multiple allowed data resources now display as read only instead of user editable

SDK

• A new package 19.139.0 was released with no breaking changes

• Fixed custom width drawers in the Uniform design system not honoring the width property

Improvements

• Opt-in for advanced search and filtering has been removed and this feature is turned on by default
• listing patterns with locale visibility rules on their root node works correctly

• Entry delete confirmation modal now closes on deletion

Bug fixes

• Fix refresh resetting the active release to base

SDK

• A new package 19.140.1 was released with no breaking changes

• Allow API key authentication in /api/v1/roles endpoint (UNI-9269)

Bug fixes:

• Filter value field no longer shows "true" or "false" when switching from "is empty"/"is not empty" to text-based operators like "contains" or "starts with." (UNI-9206)
• Dynamic path variable is now automatically populated when adding a dynamic node in the Project Map. Previously, switching the segment type to "Dynamic" before entering a node name would leave the path variable field empty, requiring manual input. (UNI-6781)
• Fixed an issue where icons were not rendering in Mesh SDK applications. (UNI-7854)
• Users with optional fields that have regex validation will no longer see validation errors when leaving those fields empty. (UNI-5941)

Uniform packages published with version 20.60.2

• Fixed bound locale race condition when creating data resources

SDK

• A new package 19.141.0 was released with no breaking changes

• Design System: fix empty (or zero) content in <Counter> component
• Fixed "scope" property not being saved in custom integrations' manifest which was preventing accessing user's mail and name in Mesh Framework
• Improved Cache Key Granularity: Fixed an issue where cache keys did not include the pattern identifier, causing components based on different patterns to incorrectly share cached values. Now, the pattern ID is included in the cache key

Improvements

• Avoid caching Custom Edgehancers results if they contain errors

Package update

• Uniform packages published with version 20.14.1.

• a new package 19.132.0 was released with not breaking changes

Bug fixes and improvements

• Add visual differentiation for patterns vs components
• Add localizable icon to custom parameters
• Adding content list data resource with single allowed type
• Add default hide locked components for children of pattern
• Link parameters no longer cause errors if saved with no changes
• Make unlink pattern a proper modal and update content
• Remove slowness when switching between lots of locales
• Do not error on loading custom integrations list
• Use base text colour for all callouts body text
• Do not show "Convert to pattern" if the node is already a pattern
• Allow long data source names up to the API stated limit
• Allow switching between variables under edit
• Don't throw if a redirect is pushed with bad data
• Purge redirect route cache on update not just insert
• Pulled getServerConfig into core rsc package to avoid it being pulled into client side bundle, added withUniformConfig to mesh experiment

• a new package 19.132.1 was released with not breaking changes

Bug fixes and improvements

• Remove teal from integration GUID copy action

• a new package 19.133.0 was released without breaking changes.

Features

• Support for control group on personalization variant, new match criteria for highest score in category, this requires an upgrade to 19.133.0

• a new package 19.134.0 was released with no breaking changes

Features

• add cache-purging webhook utilities to the mesh-edgehancer-sdk package

Bug fixes

• Fix context UI check for the ^ criteria type
• Preserve entry filter and sort options when duplicating entries
• Fix the AI integration icon display in the prompt editor
• Fix the border not showing correctly for design system menu items in certain scenarios

• a new package 19.134.1 was released with no breaking changes

Bug fixes

• Fixing various styling issue in the uniform app

• Uniform CLI: composition, composition-pattern, component-pattern, entry, and entry-pattern get/update/remove commands now validate that the provided ID matches the expected entity type. If you use the wrong command (e.g., composition remove on a pattern ID or entry-pattern remove on a non-pattern entry), the CLI will error with guidance on the correct command. (UNI-9008)
• SDK: Enable logging on Akamai EdgeWorker in the event of unexpected exception. (UNI-9009)
• API: A new option, ignoreRedirects, has been added to GET /api/v1/route, which lets you ignore redirect definitions when fetching a route. If your project doesn't use redirects, setting this may result in marginal performance gains. (UNI-8775)

Bug fixes:

• App Router SDK: Page state false positive when Test nested in Personalization with existing compressed prefix UNI-9131
• Dashboard: fixes layout and scrolling behavior in Data Resource editor (UNI-7676)
• Canvas Preview: In-context editing compositions with Next.js App Router when a redirect path also matches the composition under edit, now works correctly instead of executing the redirect (UNI-8775)
• Dashboard: fixes an issue with the missing validation of localized parameters in a project with no locales defined (UNI-8829, UNI-9140)
• API: fixes an issue with entry usage tracking where pattern data overrides were not being tracked (UNI-8911)
• Dashboard: rich text field shows "Previewing connected entry" for empty string values correctly now (UNI-9003)
• Dashboard: fixes the regression where the "Invite Team Member" drawer no longer auto-focuses the Name input field (UNI-9111).

Uniform packages published with version 20.57.1

• Improved Contentstack integration to load entries during data resource configuration by adding pagination support (UNI-7713)

Features:

• You can now get information about the usage of data sources, data types, and tests across your Uniform project (UNI-7696)

Bug fixes:

• Fixed an issue where passing false to withInstances to the /relationships API was interpreted as a truthy value (UNI-7698)
• The issue above was fixed for the following API parameters as well:
  • includePublic and teamSpecificType on /integration-definitions​
  • exactType and teamSpecificType on /integration-installations
  • includeMetadata on /members

• Rework how Uniform Context control groups work

Bug fixes

• Fix Canvas UI visual bug when preview is expanded
• Fix entry pattern editor exposing the slug editor

• Fix Release not being preserved when navigating out of canvas

• The quick create API key option on the project dashboard now lets you choose the role and name of the key to create, instead of always creating a read-only key (UNI-7695, UNI-7694)

Improvements

• Update invitation UI to use design system components (UNI-7751)
• Enhanced mesh parameter to allowing passing of composition and edition ID values (UNI-7667)

Bug fixes

• Adding multiple components to the body of a loop component will preserve child order correctly (UNI-7145)
• Enhance component definition list with updated no results UI (UNI-7145)
• Fix redirect validation to allow different domains with matching paths (UNI-7731)

Package update

Uniform packages published with version 20.30.0

• Introduced support for test variant distributions on edge workers. Requires SDK version 19.180.0 or later.

• Allow CORS for static images served by Uniform
• Respect original image cache control headers when serving external assets in the dashboard

Bug fixes

• Adjust the background color of a table header on the integration pages

• Mesh React SDK - search and filter no results found now display the correct no results message (UNI-7144)

Package update

Uniform packages published with version 20.31.0

• Improved the Rich Text parameter user experience

• CLI now supports synchronizing webhooks for API keys with team admin rights (UNI-7703)
  • Includes a change to the all CLI preset to include webhook, you will get an "Error: permission denied" if your API key has no team admin rights
  • To exclude the webhooks from the all preset, add disableEntities: ['webhook'] to your Uniform config file

Improvements

• All webhook payloads now contain a top-level eventType key which identifies the type of event that triggered the payload (UNI-7703)

Bug fixes

• Fix non-clickable area within the dropdown of the of button with menu component (UNI-7769)

Package update

Uniform packages published with version 20.32.0

• UI improvements to the redirects list

Bug fixes

• Fix API throwing an error when reading a bad block value
• Fix Canvas editor warning of unchanged value when nothing changed

• Fix nested patterns not correctly resolving single locale overrides and vice-versa (UNI-7752)

Package update

Uniform packages published with version 20.32.1

• Fix broken entry after its pattern was deleted
• Fix composition serialisation of localisable parameters during CLI sync command
• Hide "Override" tab for Slot Sections
• Fix url of "Design System" and "Mesh Framework" Storybooks

• Design System Update number and number parameter inputs to disable number wheel scroll by default to prevent unintentional number adjustments when scrolling (UNI-7626)

Package update

Uniform packages published with version 20.27.1

• Improved editorial experience for Uniform Content and Contentful when overriding Pattern data resources

• Release 19.88.0 platform and packages, no breaking changes
• Mesh SDK (React): provided default ResultItems rendering for ObjectSearchContainer component

Features

• Asset Library: data connection consistency and direct custom URL
• Content: new usage tracking UI for content types and usages tab
• Canvas: component inserter search improvements

Bug fixes and improvements

• Asset Library: hide asset delete button if no delete permissions
• Content: deterministic entry API result ordering
• CLI: fixed assets and file syncing
• Allow in slot text regression

• Release 19.89.0 platform and packages, no breaking changes
• Mesh SDK (React): default query value for Object Search Provider

Bug fixes and improvements

• Asset Library: asset selector finds assets from blocks loop
• Content Blocks: hide DnD indicator when readonly
• Asset Library: re-upload files when entry is duplicated
• Component inserter: correctly sort by “recently updated”
• Dashboard: integration category filter to use equal check instead of include
• Mesh: datatypes do not expose internal uniform content custom fields in the public API
• Content: show drawers even with left panels closed
• Context: omit unselected tests

• Release 19.90.0 platform and packages, no breaking changes

Bug fixes and improvements

• CLI: optimize CLI pushing of assets, improve error messages
• Project Map: fixing delete causing expander to go missing

• Release 19.91.1 platform and packages, no breaking changes

Features

• No changes to publicly released features

• Release 19.91.0 platform and packages, no breaking changes

Features

• CLI: adding ability to override empty source guards in config
• Edgehancers: allow to disable SWR
• AI integrations: enable prompt metadata location
• Canvas: support number or boolean bindings as display titles

Bug fixes and improvements

• Mesh: the use as default setting persistance on data resource
• Project Map: don't create composition for placeholder nodes
• Redirect Management: fix issue with trailing slashes in Route API

• Features
  • Added limits to number of items to include in a loop, as well as the ability to skip items.
• Bug fixes and improvements
  • Increased long term cache timeout to 500ms
  • Show team name on project dashboard
  • Update order for Uniform Content multi-entry
  • Batch Contentful requests

• Release 19.92.0 platform and packages, no breaking changes

Features

• Kontent.ai integration: support for surgical cache clearing

Bug fixes and improvements

• Edgehancers: improved error messages for cache invalidation
• Project Map: improve loading experience or large project map
• Canvas: structure panel doesn't allow DnD component reorganization unless pinned

• No new npm packages released.

Features

• Kontent.ai integration: support for surgical cache invalidation when using asset data types 

Bug fixes and improvements

• Component inserter: optimize loading of pattern cards

• Features
  • Webhooks for content entries
  • Option to not delete composition when deleting project map node
• Bug fixes and improvements
  • Increase clickable region for entries data resource
  • CLI update toa dd support for passing state to sync config

• Workflows role assignments now display placeholder text

Bug fixes

• Fixed an issue with override application on deeply nested patterns

• conditional-values: evaluate conditional property values on block instances (UNI-8589)

Package update

• Uniform packages published with version 20.46.0

• Resolved an issue where change detection failed when a value was set to an empty string. This fix is available in @uniformdev/context v19.210.2 and later.
• Fixed an issue where nodes in Slot Sections were missing in some compositions. Affected compositions will now function correctly.
• We've optimized the "View Source" feature for large compositions, making it load much faster.
• The default locale is now preserved when adding a new one.

• Edgehancers: Resolved an issue with entry resolution by slug when slugs were not unique across content types.
• Search: The default locale is now correctly applied to resolved data.

Improvements

• Canvas Editor: Added pattern indicators for nested patterns. Previously, the indicator was only shown for root pattern nodes. This helps identify which nodes are patterns that can accept overrides.
• Documentation: Improved the look and feel of the documentation site for easier navigation. Go to documentation.
• Project Map API: When requesting project map nodes with composition data, a modified attribute indicating the last modification date is now included. This is useful for generating sitemaps. It is available in the REST API and Project Map client v19.211.0 and later.

• Next App Router SDK: Added resolveEmptyPlaceholder support to UniformComposition, to allow customizing placeholders inside Canvas editor.

Bug fixes

• Editing the data resource name in a Loop component did not take effect in some instances.
• Changing the permissions assigned to team members was not functioning for some teams.

SDK

• New version of pacakges published: 19.209.0.

• API - Fixed an issue where IP rate limit would be erroneously applied

• Disable read-only parameters inside preview in Next.js App Router SDK (upgrade to 19.209.1 to get the fix)
• Fixed 3rd-party DAM integrations bug
• Uniform Content Data Resource's custom filter now renders drop down lists correctly

SDK

Version 19.209.1 of @uniformdev SDK (npm packages) has been released

• Reference search and filter performance improvements
• Improve CLI error handling of malformed configurations

Bug Fixes

• Reordering components in a slot section now works correctly
• Improved signal editor stability

Package updates

• Uniform packages updated to version 19.210.0 is now available for download

• a new version 19.111.0 was released with no breaking changes

Bugfixes

• Fix publishing entry twice issue
• Improve message from project map endpoint if path is too long after sanitizing

• The upgrade callout for the new Uniform Content Search is now visible only to admins.
• Enhanced search functionality for content-heavy projects.
• Kontent.AI rich-text elements now have modular content resolved and available for binding.
• The Uniform CLI's new command is now using Component Starter Kit v6 based on App Router, learn more here.

Bug Fixes

• Fixed an issue preventing direct opening of the Settings and Integrations pages.

• a new version 19.115.0 was released with no breaking changes

Feature

• Provide user Context info for integration

Bug fixes

• Gracefully handle shopify CDN 403 when resizing images
• Timestamp between list and grid views are now in sync

• a new version 19.106.1 was released with no breaking changes

Bugfixes

• Increase file upload timeout when using the CLI
• Various other improvements

• a new version 19.115.1 was released with no breaking changes

Bug fixes

• Entry list now show 12 results if the user previously had a local storage value of 10
• Fix pagination not resetting when applying filters
• Improved Entry list empty state
• Adding the possibility in mesh sdk to properly bind countValue in QueryFilter

• a new version 19.116.0 was released with no breaking changes

Features

• Grandfather upload for image URL
• Update image and asset param icons

Bug fixes

• Support "Allow all" and inherited definitions in canvas editor slot placeholder
• Fix error Vercel edge middleware to support password protected features

• Updated favicon images and other branding assets
• Better validation error messages for Asset entities

Bug Fixes

• Fixed bug with RTE editor inserting dynamic token in a wrong place.

• a new version 19.117.0 was released with no breaking changes

Bug fixes

• Better support for data resources in entry pattern instances
• ux improvements for parameter references prompts
• Mesh SDK: Avoid resetting QueryFilter count parameter to undefined
• Respect allowed content types setting for Uniform Content at the edge

• Fixed Assets API regression that made the _name a required property

• a new version 19.117.1 was released with no breaking changes

Bug fixes

• Compositions and entries now remember filter options
• Mesh SDK: drag-n-drop should not drop some of the additional properties of variables in VariableList

• a new version 19.107.1 was released with no breaking changes

Bugfixes

• Fixing 256 KB Composition size limit

• Resolved an issue where creating the first entry in a project could cause glitches.
• Fixed a problem that prevented the Entry Editor from opening in a new tab when using Ctrl/Cmd + Left Click.
• Rich Text Editor now correctly renders links to dynamic project map nodes.
• Fixed a bug that caused binding issues with blocks in specific cases.
• Quirks and Enrichments updates are now accurately reflected in the Context Manifest change count.
• Resolved an issue with cross-project file synchronization when using the CLI package.

• Edge API: Optimized fetching of localized Uniform content data resources

Uniform packages published with version 20.49.4

Uniform packages published with version 20.50.0

• Added new webhook events for asset management:asset.published, and asset.deleted

Improvements:

• Improved design system components documentation by clarifying dependencies of each component (UNI-8871)

Bug fixes:

• Fixed an issue where long project names would not be fully searchable in the project dropdown (UNI-7517)
• Fixed an issue where navigating to a composition/component pattern list from an entry list would lead to an error (UNI-7599)
• Releases widget on the project home screen now has a title again (UNI-8887)
• Fixed an issue where SearchAndFilter and SortItems components from @uniformdev/mesh-sdk-react displayed with incorrect heights in mesh locations (UNI-7853)
• Removed an inconsistent trailing slash from the project.url property in some webhook payloads (UNI-8929)
• Fixed an issue where pattern data selection menu would sometimes have no menu options (UNI-7662)

Uniform packages published with version 20.50.1

Streamable HTTP MCP transport

The Uniform MCP server now supports two transport modes, giving you more flexibility in how you connect AI assistants to your Uniform project.

Transport Options

HTTP Streamable (New)

Connect directly to Uniform's hosted MCP endpoint—no local process required. Ideal for web-based tools, cloud environments, or anywhere running a local process isn't practical.

{
  "mcpServers": {
    "uniform": {
      "url": "https://ai.uniform.app/projects/<your-project-id>/mcp",
      "headers": {
        "x-api-key": "<your-api-key>"
      }
    }
  }
}

Stdio (Existing)

Run the MCP server locally as a process. Best for desktop tools like Claude Desktop or local development setups.

{
  "mcpServers": {
    "uniform": {
      "command": "npx",
      "args": ["-y", "@uniformdev/uniform-mcp"],
      "env": {
        "UNIFORM_API_KEY": "<your-api-key>",
        "UNIFORM_PROJECT_ID": "<your-project-id>"
      }
    }
  }
}

Bug fixes:

• CLI: Improved cli login visuals and fixed a copy to clipboard overflow issue (UNI-8313)
• Canvas: Fixed an issue where a failed data binding would cause a wrong validation error (UNI-8806)
• Dashboard: Fixed an issue where navigating back from the block editor (when accessed from a composition) would incorrectly lead to the content types list instead of the original composition (UNI-8641)
• Permissions: Prevent users with read-only access to assets from saving or modifying asset details (UNI-8165)
• Usage tracking: Fixed an issue where some entries were not tracked properly when referenced inside of a "Multiple entries" archetype
• Usage tracking: Unused data resources are now excluded from the usage data (previously just adding but not referencing a data resource would count as usage)

Package update:

Uniform packages published with version 20.49.3

• No new npm packages published.

Only internal dependency update, no new features of bugfixes.

• New integration with Bynder DAM has been released, allowing to instantly access your assets from Bynder in Uniform visual workspace. Check out docs here.

SDK

• No new npm packages published.

Improvements

• Minor UI change to update modal styling.

• Show preflight warnings for unpublished optimization references

Bug fixes

• Disable strict schema warnings for the JSON parameter
• Rich Text Editor links are now reflecting the selected node in the modal
• Update filter handling to show the correct Search and Filtering UI
• Fix an edge case where a false missing component definition validation error was shown
• Converting overridden localizable values to not localizable now works as expected
• Sort data resource listings alphabetically

• Npm packages version 19.96.0 were published. No breaking changes.

Features

• The relationships (usage tracking) API is now marked as stable
• Added usage tracking check prior to CT deletion

Mesh integrations

• Two archetypes: Single Product and Multi products
• Native locale support
• Certain fixes and tweaks via custom edgehancer to make commercetools API work with our Data Types
• commercetools v2 (Parameter Types aka enhancers) integration was moved to Classic category

Bug fixes and improvements

• Project map: Bringing back redirect data
• Fixed regression with the modal display

• No SDK changes

Features

• Expose thumbnail field/param on content type/component

Bug fixes and improvements

• dashboard: content or block types now create or duplicate correctly

• No SDK changes

Features

• Canvas: Enable 100-char long public IDs for component and content type definitions
• Dashboard: Entries and content types filtering UI design refresh

Bug fixes and improvements

• Files: prevent unwanted file deletions, add logging around deleting files 

• A new package is out 19.99.0 with no breaking changes

Early access features

• Support different preview modes and preview URL change flow improvements.

Features

• Content type-level permissions for entries
• Allow using assets for component thumbnails

Bug fixes and improvements

• Allow data types with very long content type public IDs
• Design System: design improvements to input fields

• A new package is out 19.100.0 with no breaking changes

Early access features

• Support different preview modes and preview URL change flow improvements.

Features

• canvas: add a new property to DataSource - customPublic to store not encrypted global connector settings
• mesh-sdk-react: move useContentDataResourceLocaleInfo to mesh-sdk-react to re-use platform logic in mesh integrations

Bug fixes and improvements

• canvas: composition defaults can have locales
• canvas: link param keeps locale input value between nodes
• canvas: prevent editing non-overridable PDR from DR list
• assets: use asset title for display value
• canvas: design tweaks for entry patterns

• no packages included in this release

Bug fixes and improvements

• Dashboard: update entry thumbnail conditional check and design tweaks

• A new package 19.102.0 is out with not breaking changes
• @uniformdev/canvas-next: add default modifyPath callback for i18n support, see examples in our new localization starter for Next.js here.

Mesh Integrations

Updated integrations for Contentful, Contentstack, commercetools and Kontent.AI with the following improvements:

• Automatic locale binding, if your project have dynamic locales enabled
• Regressions of backward compatibility and explicit static locale usage fixes
• Refactoring of Object Search components usage

Bug fixes and improvements

• Mesh: allow number fields to be bound to string values
• Project Map bugfix method Route.match should ignore trailing slashes.
• UI: entries and compositions filters no longer reset or have a delayed typing within the search term

• The type property added to entries and composition webhooks
• Locales menu with many locales now scrolls
• Fix the page reload on a pattern first save
• Fix scrollbar issue when hovering or selecting a parameter 

• 19.92.2 npm packages published. No breaking changes. Dependency updates.
• Mesh SDK (React): fix ObjectSearchFilter selectOptions property to make it respect value property

Features

• Asset Library: track and report fair-use metrics

• a new version 19.105.0 was released with no breaking changes

Bug fixes and improvements

• Fix dynamic parameters not considering localized values on the API

• a new version 19.106.0 was released with no breaking changes

• 19.92.3 npm packages published. No breaking changes. Dependency updates.

Features

• CLI: support publishable flag for entries

• No new packages were published

Features

• Dashboard: block fields now show within the entry structure panel

Bug fixes and improvements

• Component name now displays correctly in link param project map link selection
• Edgehancers: sync validation schema with MergedDataType interface

• No new packages were published

No platform features were released today.

Chrome extension update

A new version of our Uniform Toolbox Chrome extension has been released, here are the changes:

• Feature: ability to copy a single composition or entry - now when you're editing a composition or entry, you will get a new button in the extension popup to copy it to clipboard (instead of a whole project). You can then paste it in another project (for copying within the same project you can simply use the native duplicate feature).
• Bug fix: incorrect detection of whether to publish a composition/entry

• Npm packages version 19.94.0 were published. No breaking changes.
• Canvas React SDK: added ability to iterate through componentStore collection
• Design System: respect rich text readOnly prop changes

Features

• Context: Ability to use A/B testing via Uniform Contentful and Contentstack apps.

Bug fixes and improvements

• Component inserter: improved search performance
• Context: remove catch all in context dev tools plugin to avoid duplicate messages being sent to chrome extension
• Dashboard: variable menu no longer displays under another element
• Edge personalization: remove response.ok condition from decision whether or not to rewrite HTML

• OpenAI integration:
  • support for DALL·E 3 image generation
  • ability to customize the amount of images to generate per prompt, as well as globally
  • global override of models
  • misc cosmetic fixes and dependency updates
• OctoAI integration:
  • Customization of the amount of images to generate per prompt and globally
  • misc cosmetic fixes and dependency updates

SDK

• Npm packages version 19.95.0 were published. No breaking changes.
• Integration SDK: allow explicitly disabling scrollbar in iframe for mesh locations
• App Router / React Server Components:
  • emit personalization and test events on RSC server rendered tests
  • handle control values over 1 to account for manifest values
  • enforce preview secret on RSC preview POST endpoint if configured

Features

• Dashboard: add separate creation flow for content types and block types

Bug fixes and improvements

• Dashboard: Safari modal hides content with height: auto

• A clearer, more focused visual editor: read the announcement

Improvements

Improved Route API Cache Efficiency with Query String Filtering

We've enhanced the Route API to provide significantly better cache hit rates for sites using dynamic URL parameters. Previously, all query string parameters were included in cache keys, meaning URLs with visitor tracking IDs, analytics tokens, or other dynamic values would each create separate cache entries—potentially exhausting your cache quota and triggering rate limits even when requesting identical content. The Route API now automatically filters query strings at the edge, recognizing only the parameters you've explicitly configured in your project map (both globally and at the node level). For example, if you've configured color as an allowed query string, requests to /page?color=red&visitorId=abc and /page?color=red&visitorId=xyz will now resolve to the same cache entry, since visitorId is unrecognized and ignored.

Existing projects will allow all query strings until you trigger save your project map or modify a data type; after performing one of these actions, only your explicitly configured query strings will vary the cache.

Scout improvements

Our AI agent Scout has received significant updates to make it more capable and reliable.

• Stop button: Abort in-progress Scout responses at any time.
• Smarter slot handling: Scout is much better at understanding and working with slot sections.
• Pattern expertise: Dedicated pattern tools make Scout significantly better at creating and using patterns.
• Uninterrupted responses: Changing the chat position while a response is in progress (e.g., moving to sidebar) no longer interrupts Scout.
• Entries or compositions created by Scout while a release is active now redirect to the correct edit URL.
• General performance, accuracy, and user experience enhancements.

Other improvements

• Canvas - Empty read-only slots of a pattern are now hidden from the structure panel
• Navigation - Reordered team security page sub navigation

Bug fixes

• Rich Text - Fixed a bug where column and row headers control did nothing

Package update

Uniform packages published with version 20.47.1

• Context: Prevent transient signals from losing state when partial updates are passed to context
• Dashboard: Fix reference filter UI not showing for some search editors, selected options no longer show in the references options list

Improvements

• Design System: Fix react warning inside ObjectGridItem component
• CLI: The CLI --config argument no longer incorrectly extends uniform.config.ts (regression in 19.212-19.213)

Package update

• Uniform packages updated to version 19.214.0 is now available for download

• Canvas: save button sub-menu "Unpublish" menu item label changed to "Unpublish in release" when inside an active release (UNI-8777)
• Webhooks: Project Map update event projectmap.update payload now includes an initiator property, consistent with other project map webhook event types (UNI-8721)

Bug fixes:

• Issues with the number parameter type have been resolved (UNI-8745)

Package update

Uniform packages published with version 20.48.0

• Loading large compositions and patterns into the editor is now significantly faster

Project Map improvements

The project map has had visual design updates and some flow changes around editing a project map node.

• The currently selected project map node is now automatically scrolled to in long lists (i.e. link fields, moving nodes, redirects, etc)
• You can now manage the attached project map node of a composition directly from the composition editor for tasks such as updating or translating path segments.
• Improved the redirect detection method so we only show the redirect checkbox if the node is truly being moved.
• You can now move a project map node when in the edit drawer
• Reordering project map nodes is more consistent
• Fix associated with duplicating a project map node several times in a row
• Locales and query string forms have now been moved to a nested drawer
• Adding multiple links within a rich text field to the same dynamic project map node works correctly
• Various bug fixes

SDK v20

• The @uniformdev/canvas package is now compatible with Node 22.
• Next.js 15.1 is now supported for App Router.
  ⚠️ Older versions of Next.js are not compatible with Uniform v20 when using App Router.

SDK Breaking changes

We’ve released a new major version of our SDK v20.0.0, with the following breaking changes:

• canvas: the localize() function's deprecated legacy props format has been removed. The LocalizeModernOptions type was also renamed to LocalizeOptions.
• canvas: the walkComponentTree() function has been removed. Use walkNodeTree() instead.
• canvas: the ComponentLocationReferenceV2 type has been renamed to ComponentLocationReference.
• canvas: conditional visibility related functions are no longer marked deprecated [now considered stable]
• canvas: the CompositionGetOrderBy type was removed. This was no longer used.
• canvas: the CompositionIssue type was removed. Use DataResolutionIssue instead.
• canvas: the CompositionPatternIssue type was removed. Use PatternIssue instead.
• canvas: the CompositionDiagnostics type was removed. Use EdgehancersDiagnostics instead.
• canvas: the CompositionDataDiagnostic type was removed. Use DataDiagnostic instead.
• canvas: the ProjectMapLinkComponentParameterValue type was removed. Use ProjectMapLinkParamValue instead.
• canvas: the LinkComponentParameterValue type was removed. Use LinkParamValue instead.
• canvas: the getPropertyValue() function was removed.
• canvas: the following legacy preview related functions have been removed: createEventBus(), getChannelName(), and subscribeToComposition()
• canvas-react: the children property was removed from UniformPlaygroundProps. It had no effect already.
• canvas-react: the UniformSlot component no longer accepts children. Use the wrapperComponent prop instead. See migration guide below.
  note: this does not affect app router.
• canvas-react: the useCompositionEventEffect() hook has been removed.
• canvas-vue: the useCompositionEventEffect() hook has been removed.
• cli: the pattern command, as well as using pattern in the sync config, no longer exists. Use componentPattern, compositionPattern, and entryPattern instead.
• cli: we no longer consider legacy file sync location when doing a pull/sync (last used in packages older than v19.88.0). You can re-pull your project if you have old backups.
• cli: The legacy CLI file hashing was removed. This will only affect apps using a CLI version older than v19.88.0.
• context-devtools: the <ToggleEmbeddedContextDevTools /> component has been removed. Use the Context Chrome extension instead.
• mesh-sdk-react: The following deprecated components have been removed:
  • ProductPreviewList
  • ProductQuery
  • ProductSearch
  • ProductSearchRow
  • ProductSelectedItem
  • SelectionField
  • DamSelectedItem
  • DefaultSearchRow
  • DefaultSelectedItem
  • EntrySearch
  • ResolvableLoadingValue
  • These components are replaced with ObjectSearch* components
• mesh-sdk-react: the countValue prop has been removed from the QueryFilterProps type
• mesh-sdk-react: the label property has been removed from the ObjectSearchFilterContainer component
• mesh-sdk-react: the id and name have been removed from the ObjectSearchFilter's selectOptions prop. Use label and value instead.
• mesh-sdk-react: the name and subtitle props have been removed from the SelectedItemProps type. Use title instead.
• mesh-sdk-react: the image prop has been removed from ObjectSearchListItem - use imageUrl instead.
• mesh-sdk-react: the isMulti prop has been removed from ObjectSearchListItem - use the isMulti prop on ObjectSearchProvider instead.
• mesh-sdk-react: Search & Filtering-related types are no longer in beta.
• mesh-sdk-react: The disableReset prop has been removed from InputVariables - the computation is now automatic. The showMenuPosition prop is no longer deprecated as it is shipped.
• mesh-sdk-react: the hasReferencedVariables() function is removed. Use the same function from @uniformdev/canvas instead.
• project-map: Editions-related types are no longer marked deprecated as the feature has shipped.
• design-system: The <Badge/> component has been removed. <Chip /> can be used instead.
• design-system: The withoutPortal prop has been removed from <ButtonWithMenu />. Use portal instead.
• design-system: The isIndented and isCompact props on <Details /> are no longer beta/deprecated
• design-system: The MediaCard component is removed. Use the <GridListItem /> component instead.
• design-system: The IntegrationHeaderSection component has been removed.
• design-system: The menuLabel prop is removed from <Menu />. Place a label on the menu trigger instead.
• design-system: The forceVisible prop is removed from <Menu />. Use the open prop instead.
• design-system: The <MenuItemHeading/> component is removed. Use <MenuGroup /> instead.
• design-system: The wrapperClassName prop is removed from <Modal />
• design-system: The isBound prop is removed from <LabelLeadingIcon /> - use isActive instead.
• design-system: The ConnectToDataElementButton component is removed. Use <LabelLeadingIcon /> instead.
• design-system: The ParameterDataResource component is removed.
• design-system: The baseId prop on <Popover /> is removed.
• design-system: Props related to parameter overriding are no longer marked deprecated, they are stable.
• design-system: The <ProgressBar /> component is no longer marked beta
• design-system: The <ShortcutRevealer /> and <ShortcutContext /> components are removed. Use useShortcut instead.
• design-system: The asSpan prop has been removed from the Heading component. Use as=span instead.
• design-system : The <AnimationFile /> component has been removed. Use <LoaderOverlay /> or <Spinner />
• design-system: Removed reakit completely in favour of ariakit
• design-system: Refactor <Button /> component to use ariakit
• design-system: Refactor <ButtonWithMenu /> component to use ariakit
• design-system: Refactor <DateTimePicker /> component to use ariakit popover
• design-system: Update broken props after refactor on <IconButton />
• design-system: Remove unused capture prop which was only present for reakit fix on <Input /> and <Textarea /> components
• design-system: Refactor <Tooltip /> from using reakit to ariakit
• design-system: Remove reakitfrom package.json
• storybook: Remove red styling on boolean inputs
• context-ui: Remove reakit dependency
• context-devtools: Remove reakit dependency

Migration guides

Migrate from UniformSlot children to wrapperComponent

Before:

import { UniformSlot } from '@uniformdev/canvas-react';

export const Carousel = () => {
  return (
    <div className="carousel">
      <UniformSlot name="slides">
        {({ child, component, key }) => (
          <div className="carousel-item" key={key}>
            {child}
          </div>
        )}
      </UniformSlot>
    </div>
  );
};

After:

import { UniformSlot, UniformSlotWrapperComponentProps } from '@uniformdev/canvas-react';

export const Carousel = () => {
  return (
    <div className="carousel">
      <UniformSlot name="slides" wrapperComponent={CarouselItemsWrapper} />
    </div>
  );
};

export const CarouselItemsWrapper = ({ items }: UniformSlotWrapperComponentProps) => {
  return <div className="carousel-items">{items}</div>;
};

Next.js 15.1

The React Server Components packages have been updated to target Next.js 15.1. This update introduces several breaking changes, including the conversion of certain synchronous functions to asynchronous. As a result, these functions must now be awaited before use.

To facilitate a smooth transition, refer to the official Next.js 15.1 upgrade guide provided by Vercel. The guide includes helpful codemods to streamline the upgrade process.

Key Highlights of Next.js 15.1

• React 19 Support
  Next.js 15.1 now supports React 19, which has reached stable status. You can continue using React 18 or integrate with 19 into your projects confidently.
• Turbopack Enhancements
  The uniform.server.config.js configuration file now supports Turbopack. Additionally, TypeScript can be used to define your configuration.
• Fetch Caching Updates
  Changes to fetch caching behavior in Next.js 15 impact how cache strategies are applied. By default, fetch calls without a specified cache strategy will no longer be cached. For more details, refer to the caching semantics documentation.
  If you are using Uniform’s exported functions and pre-configured clients to retrieve data from our APIs, rest assured that caching behavior will remain consistent with previous versions. This is because Uniform explicitly defines a cache strategy for every request.

For additional details about the changes in Next.js 15 and 15.1, consult the resources below:

• https://nextjs.org/blog/next-15-1
• https://nextjs.org/blog/next-15

• "Recent compositions/patterns/entries/etc" lists were fixed and got improvements to work on multiple projects
• "Sort by" value is now saved in Uniform Content query data resources
• Fixed the issue with adding new components at the end of a non-empty slot
• Fixed Drag&Drop in Canvas Editor's structure tree

Improvements

• JSON viewer now allows collapsing nodes
• Optimisations to API caching for Data Types with explicit cache bypassing

• Fix "The value must be an array" being shown for asset param when binding data is missing (UNI-8754)
• Fix long component pattern name overflow issue within the component card popover within canvas (UNI-8591)
• Fix a flash of no roles found for admin users when initially loading the roles listing (UNI-8675)
• Fix an issue whereby users with read-only data type permission would see the test data type button disabled (UNI-8095)

Improvements:

• Update role project listing sort order to display in alphabetical order (UNI-8710)

Package update:

Uniform packages published with version 20.49.1

• Fixed an issue where localizability of read-only parameters was editable
• Fixed an edge case where block fields were not editable if a value in another locale was bound
• Fixed an issue where locales set when creating a composition through a project map were not respected

Improvements

• We no show a validation error in the UI when disallowed characters are entered as part of a project map node path.

• When a child variant of an A/B test is selected, the preview sometimes displays different variant (UNI-8793)
• Add ignored query strings to Route API diagnostics output (UNI-8735)
• Fix a bug preventing preview to load when unrelated permission was not granted (UNI-8312)
• Fix copy icon visual regression (UNI-8497)

Package update:

Uniform packages published with version 20.49.2

• Improved the speed of CLI asset syncing

Fixes

• Insights now allow for optional project ID when using proxy mode
• When resetting a parameter override in a pattern that uses another pattern, the value now resets to the parent pattern's override value instead of the base pattern's original value.

Package update

• Uniform packages updated to version 20.2.0 is now available for download

• Canvas Editor: Correctly render Locale as dynamic parameter.
• Canvas Editor: Uniform Content Query data type filters are not reset now, when changing sorting order.
• Canvas Editor: Reloading Pattern Data Resource works correctly now

Improvements

• API: New parameter in Uniform Content Query to specify total count of entities to fetch.
• Canvas Editor: Component Inserter modal is bigger now

• Context browser extension: Fixed an issue in the Context Chrome extension where an error message would incorrectly appear if a project had no signals, even when other dimensions (like enrichments) were present and overridable. The extension now correctly identifies all overridable dimensions and only shows an error if none are available. (UNI-8620)
• Workflows: Fixed several edge-cases where workflow stage permissions were overly restrictive (UNI-8537, UNI-8548)
• Data types: Removing a query string or header value from the data type editor now maintains correct visual state (UNI-8604)
• Canvas: Fixed an issue where number parameter value would be saved as a string (UNI-8651)

Improvements

• CLI: Pushing a component definition with no parameters property now prints a warning (set the property to an empty array to remove all parameters) (UNI-8652)
• API: Improved the performance of redirects resolution when querying the /route API (UNI-8678)

Package update

• Uniform packages published with version 20.47.0

• Canvas Editor: Assets now show in Rich Text when bound from Uniform Content
• Canvas Editor: Removing all assets from a parameter now clears the parameter value
• Canvas Editor: Fixed a bug where an entry slug would be regenerated when it was not supposed to
• Mesh: Custom fields and parameters now show up correctly within the conditional values panel
• Route API: Fixed a Route API 404 when multiple locales were assigned identical path segments
• Optimization: Fixed not being able to start a string with a number in a signal match field

Improvements

• Canvas Editor: Component inserter layout improved for certain screen sizes
• Canvas Editor: Content data resources now allow saving empty values
• Canvas Editor: Reference button label improvements

• Non-localized link parameters targeting project map routes with localized paths now use the localized path when requested in a specific locale from the composition, entry, and route APIs (UNI-7552)

• Fix error icon on Uniform Context Signal edit page
• Fix Paste component/pattern button in Preview panel

• Starting from version 19.169.0 of @uniformdev/cli, composition patterns (patterns created from composition types) will no longer be included by the component-pattern commands or the componentPattern config entity.
  To pull or push composition patterns, please use the beta composition-pattern commands and the compositionPattern config entity.

• It is now possible to connect dynamic inputs (e.g., query parameters) to the Limit and Skip settings of the Loop component.

• Added support for specifying a compatibilityDate parameter when deploying a Custom Edgehancer worker via the CLI.
  You can now optionally set a compatibilityDate to indicate the targeted support level in the Workers runtime. This ensures that any backwards-incompatible changes made to the runtime after the specified date will not affect the deployed worker. (UNI-7598)
• Added retry logic to Uniform CLI commands to handle occasional connection reset problems on Windows machines (UNI-7576)
• Using the Uniform CLI to push compositions, entries, or patterns that enable locales that are not registered with Uniform will now log a warning.
• Increased the latency threshold for data resource warnings from 200ms to 1000ms

Bug Fixes

• Pulling entry patterns with the Uniform CLI into a package file works correctly.
• In the Canvas editor, the option to attach to the project map is now hidden for users without the necessary permissions (UNI-7568)
• In the Properties side rail, component patterns are now correctly labeled as "Component Pattern" instead of "Composition" (UNI-7121)
• Fixed visual overflow issues with the Date/Time parameter (UNI-7415)

Package update

Uniform packages published with version 20.25.0

• Fixed issue where users could not save numeric signals.

• (CLI) Resolved an issue where component and composition patterns weren't properly syncing to Uniform package files. This ensures your patterns are correctly updated when you make changes (UNI-7444)

Improvements:

• (API) The API now supports storing larger entry and composition payloads, allowing you to work with more complex content structures without size limitations (UNI-7448)

Package update:

• Uniform packages published with version 20.23.0

• New beta component to render items in <ObjectList> as an alternative to <ObjectGridItem> - <ObjectListItem>
• New component in Design System - <DragHandler>
• New property to add icon to <MenuTrigger> component

• Visual editor:
  • now the current selected component is always visible in the property panel, while it used to only be available in the "Content" tab previously
  • improved indicator for components and patterns
• Design system: New IconColor prop and icon theme accent-alt-dark added to <Chip /> component

• Nuxt Module: Added support for Nuxt 4. The module remains compatible with Nuxt 3 (UNI-7643)

Improvements

• Consolidated Mesh Framework manifest schema for all three different tools: projectTool, dashboardTool, editorialTool (UNI-7623)
• Context packages: Removed dependency on uuid in context and context-vue, resolving ES module issues in Nuxt 3.17.6+ (UNI-7575)

Bug Fixes

• Fix issues with incomplete results being returned when using "starts with..." filtering operator UNI-7631

Package update

Uniform packages published with version 20.26.0

• Improve text truncation behaviour on long workflow name values
• Enable workflow stage filtering on entry patterns and advanced filtering

• Uniform CLI entry and entry-pattern get and list commands can fetch entries with block IDs preserved UNI-7644
• Add validation message for workflow name length UNI-6994

Bug Fixes

• Fix a link parameter project map node editor being unusable on smaller screens UNI-7470
• Fix Uniform "Entry by slug" data type missing a default locale in a data type test drawer UNI-7609
• Resetting data resource filters now sets the filters to a blank state UNI-7289
• Fix an infinite loading state in certain cases when navigating to the entry pattern editor UNI-7297

Package update

Uniform packages published with version 20.26.1

• Uniform Content Unpublished mode is now enabled by default for all new projects (UNI-7645)

Bug Fixes

• Mesh Fixed the invisible side rail button for "Canvas Editor" mesh location (UNI-7671)
• Project Map Node picker now appears correctly on smaller screens (UNI-7470)

Package update

Uniform packages published with version 20.26.2

• Allow creation Block Types in the empty Project or before any Content Type is created

• Improved the invitation flow - pre-fill invitee email and redirect to login if they already have a Uniform account (UNI-7446)

• Minor visual fixes for API Key and Team Member management (UNI-7544)
• (SDK) Fix Typescript types for in/nin filtering operators (UNI-7563)

Package update:

• Uniform packages published with version 20.24.0

• New packages 19.159.0 with updated support for Next.js App Router.

App Router / React Server Components SDK updates

• Support for <Suspense /> and component streaming. Doing some async work in your server components and want to wrap the component in a Suspense boundary? Previously, you would need to handle this in your implementation but now you can let Uniform handle this for you. The resolveComponent function on UniformComposition can now return a suspense object to specify the component. After this is configured, this loading component will be used if your component has an uncached fetch call and the actual component will be streamed in after.

resolveComponent={({ component }) => {
  let result: ResolveComponentResult['component'] | undefined = undefined;
  let suspense: ResolveComponentResult['suspense'] | undefined = undefined;

  if (component.type === 'page') {
    result = PageComponent;
    suspense = {
      fallback: () => <div>Loading...</div>,
    };
  }

  return {
    component: result ?? DefaultNotImplementedComponent,
    suspense,
  };
}}

• Additional API: retrieve compositions by slug: A helper function was introduced to fetch compositions by slug instead of by route path. This function can be useful when you are trying to retrieve a composition that is not associated with the current one but still want to benefit from built in cache logic.

import { retrieveCompositionBySlug } from '@uniformdev/canvas-next-rsc'; 

// somewhere in your component
const composition = await retrieveCompositionBySlug({ slug: 'composition-slug-here' });

• Cache optimization: route fetch requests have been optimized and requests without data in Next.js Data Cache will fall back to Uniforms CDN cache as a second layer. This will improve performance of any cache misses that occur.
• Next.js 15 RC support: new major version of Next.js is coming, see changelog is available here. This update to Uniform SDK is putting the foundational support for this upcoming release. As part of Next.js 15, the default fetch cache strategy will be changing, which you can read about here. In short, fetch requests are no longer cached by default. Uniform exports and uses the following API clients in the @uniformdev/canvas-next-rsc : getDefaultCanvasClient, getDefaultManifestClient, getDefaultProjectMapClient, getDefaultRouteClient. If you are using any of these clients, you will not see any change in caching as we always specify the cache field used to control caching.

Other bug fixes

• prevent redirect loop when locale URL equals fallback

• Fix issues with binding of the locale in data resources after locale mappings have been cleared (UNI-6516).

• Prompts navigation item in project settings now only appear for users with appropriate access permissions (UNI-7059)
• Localized fields with links to project map nodes that have localized paths work correctly (UNI-7376)
• Double-clicking a project map node in links now maintains dynamic input values (UNI-7371)

• Webhook events related to Project Map Nodes now have locale-specific path and name

Bug fixes

• Do not load single entry data resource if no entry Id was provided

• Added the option to hide the component pattern in parameter error handling

Bug fixes

• Fix signal editor refreshing on browser tab refocus
• Fix search and filtering z-index issue when configuring data resources

• Navigating away from an entry editor while using the entry preview feature no longer throws an error (UNI-7404)

Package update

• Uniform packages published with version 20.20.3

• Fixed search index initialization for programmatically created projects

• Preview mode and viewport size settings are now saved, so your preferences remain consistent across editing sessions.
• Pattern previews now load faster and no longer require CORS headers (UNI-7365).

• Fixed pattern categories filtering.

• Added optionalPatternParameter option for data resources. When true, the data resource does not create an error forcing the choosing an override value when there is no default.

Improvements

• Improved display of Test and Personalization containers in the structure and preview panels.

• Content entries can now be used as data resources in other entries, allowing you to dynamically include shared field values like product names, pricing, or terms through dynamic tokens (UNI-5826).
• Improved the reliability and performance of the NESI edge worker, with memory usage optimized by up to 24% on some platforms (UNI-7344).

Bug Fixes

• Fixed a bug in edge worker A/B testing logic that could lead to unequal variant distribution when a variant included only nested personalization.
• Fix "starts with" search operator to match only prefixes of textual fields (UNI-7327).

Package update

• Uniform packages published with version 20.20.0

• Improved server-to-client Context state transition

Bugfixes

• Fixes navigation links to be aware of active release

• Fixed Algolia entry selector UI by adjusting its hight
• Updated Kontent.ai branding
• Fixed Contentstack Data Source environment setting value saving
• Fixed parsing JSON response in OpenAI integration

• Added buildOriginRequestHeaders option to createUniformEdgeMiddleware for Vercel edge, allowing custom headers to be passed to the origin request (UNI-8973)

Bug fixes:

• Fixed an issue where the "Add Node" form would lose the entered node name if a single component definition was pre-selected (UNI-6242)

Uniform packages published with version 20.53.0

• a new version 19.124.0 was released with no breaking changes

Features

• Update composition and components Listing and filtering UI

Bug fixes

• Fix a 400 error when reloading a data source
• Creating a new entry now responds to first click interaction, publishes status menu options; label click event now triggers correctly
•  Entry slug value now truncates to prevent type cell shrinking
• Update add an entry button styles
• Fix performance issue when deleting files

• a new version 19.125.0 was released with no breaking changes

Features

• Indicate if a parameter or field is localizable on the listing

• Move project dashboard header section into the tabbed area (UNI-8998)
• When adding locales to a composition with patterns on it, pattern data in the added locale is now reliably visible without refreshing the editor (UNI-7326)

Bug fixes:

• Fixed an issue in NESI edge processing that caused errors when a personalization has zero variants. (UNI-8981)
• The preRequest hook's dataResource type now includes the variables property, matching the runtime payload. Previously, accessing dataResource.variables in a preRequest hook caused a TypeScript error (ts2339), even though the data was available at runtime (UNI-8845)
• Fixed unusual cases where the _patternOverrides property would be mistakenly propagated to route API responses (UNI-7326)

Uniform packages published with version 20.53.1

• a new version 19.125.1 was released with no breaking changes

Bug fixes

• Indicate l10n and integration on params list
• Add disabled state to content type input and filter item option
• fix default sorting issue in EntryList component when switching between old and new search and filter feature flag UI
• fix asset files being deleted due to faulty db comparison

• Fixed a bug causing slight deviation in audience distribution towards the first variation in A/B tests.
• Resolved an error that occurred when sending invitations with role-based permissions.

• a new version 19.126.0 was released with no breaking changes

Bug fixes

• Add path resolver function to app router preview handler in canvas-next-rsc
• Fix playground handler ID parameter handler in canvas-next-rsc
• Fix a bug where entry PUT would return the wrong status

• Added a new activeReleaseId property in canvasEditorTools and dataResource mesh location metadata. As opposed to releaseId which is only present when the entity being edited has been copied to the active release, activeReleaseId is always provided in a non-base release. (UNI-8928)

Bug fixes:

• Fix the popover behavior within Canvas when interacting with the preview Iframe (UNI-8843)
• Fixed an issue whereby the undocked siderail within Canvas would overlap the release drawer (UNI-5708)

Uniform packages published with version 20.54.0

• a new version 19.126.1 was released with no breaking changes

Bug fixes

• Expose data source customPublic property to custom edgehancer handlers in mesh-edgehancer-sdk

• no new package

Bug fixes

• Fix redirect warning and error text collision 
•  Apply asset overrides to preview composition

• Copying reference fields between locales now correctly sets localization for the localized values (UNI-8838)

Uniform packages published with version 20.55.0

We added a new type of Generative AI prompt called Multiple text parameters to access the whole Composition's component data or the entire content Entry.

• a new package 19.128.9 has been released with no breaking changes

Features

• Introduce bindable variable values to Records to fetch (limit) and Start from (offset)

Bug fixes

• Remove display name field from ContentTypesList component
• fixed how path is constructed for client context update, removed slug resolution + error in react server components

• Fixed an issue where an asset pasted into a rich text parameter would sometimes not be editable in the asset library(UNI-9004)
• Block properties on pattern instances are correctly shown as read-only(UNI-9020)

Uniform packages published with version 20.55.1

• a new package 19.129.0 has been released with no breaking changes

Bug fixes

• fix audience selector that is missing on the prompt inputs screen
• Allow inserting after patterns in preview panel
• Add error handling callout component to entry list and uniform content data resource editors
• Data type and data source actions menu to use portal rendering to prevent z-indexing issues
• Prevent errors updating HTTP data sources

• a new package 19.130.0 has been released with no breaking changes

Features

• use node 18+ compatible proxy implementation in uniform CLI

Bug fixes

• Enable hiding ro pattern params on slot children in Canvas

• API: fix issues with project map node invalidation when reattaching compositions (UNI-9007)
• RSC: Resolved a compatibility issue with component deserialization in React Server Components. (UNI-9050)

Uniform packages published with version 20.55.2

• No new package release

Features

• Showing a suggestion in the highlighter when only one option is allowed (excluding system components.)

Bug fixes

• Date picker allows selecting using default date
• Various fixes for pattern visual editing issues

• Releases now support descriptions
• Improved releases navigation (Scheduled, Unscheduled, Launched)
• The release list views now also includes the count of changes within the respective releases
• When editing an entity that has copies in other releases, we now show that information in a release bar

Bug fixes:

• Correctly display email links in the link parameter field. (UNI-5819)
• Fix user experience in the Canvas editor when viewing errors in the Data Resources tab. (UNI-7720)

Uniform packages published with version 20.56.0

• Modified Reference Editor to disable the Remove option when in read-only mode. (UNI-8547)
• Prevented the creation of multiple dynamic pages at the same level, resolving a configuration issue that led to broken previews and rendering failures. (UNI-8926)
• Fixed a bug where Personalization, A/B Test, and other components with inherited slots inside Slot Sections would ignore the Slot Section's component restrictions. (UNI-8894)
• Fixed an edge case with custom edgehancers where a wrong pre-request hook would be called (UNI-8949)

Uniform packages published with version 20.50.2

• a new version 19.120.0 was released with no breaking changes

Bug fixes

• AI: Fix dirty state for multi text params; hide AI-generated icon if there is no multi param prompt available
• blocks: do not offer to edit link block
• Set a maximum width on filter dropdowns on the dashboard
• limit QS parameter for edge collection-endpoints

• a new version 19.121.0 was released with no breaking changes

Bug fixes

• Ability to open inline preview url update modal from error list 
• Add datetime fallback for browsers that don't have modern intl API
• Prevent throwing when an invalid binding is in a loop
• Prevent errors when nodes are not found in a project map
• Throw response error for consecutive slashes instead of 500 in project map
• Fix API regression with composition data in project map
• Prevent error when no rights to team in project map

• Fixed an issue where enrichments that had sort order defined would not be properly grouped by their enrichment category when displayed in the enrichment tag list (UNI-8450)
• Renaming patterns (components, compositions, entries) or compositions now saves correctly when using the Ctrl+S / Cmd+S keyboard shortcut. Previously, the name would revert to its old value after refreshing the page (UNI-8888)
• Fixed an issue whereby the redirect callout would not appear when changing a path segment in the Canvas editor (UNI-6678)
• Fixed icon spacing in dropdown buttons at small size (UNI-8914)

Package update:

Uniform packages published with version 20.51.0

• a new version 19.122.0 was released with no breaking changes

Features

• Document and allow team admin api keys to deal with team members
• Enable unpublishing from composition/entry editors

Bug fixes

• fix release deletion deleting base instances

• Fixed an issue where overrides inside nested slot sections weren't working as expected.

• Asset Library now supports more file types: .txt, .md (UNI-9343)

Improvements:

• Improved error messages when attempting to create project map nodes with duplicate paths (UNI-9314)
• Release bar now indicates "outdated" if the Base version of an item has been updated since the release version was created. Mirrors and makes visible the existing release preflight warning. Other release bar wording updates for clarity (UNI-9142)

• Granular roles: Permissions for components, content types and AI Prompts can now be individually granted

Package update

• Uniform packages published with version 20.15.0

Updated integration for Algolia with the following improvements:

• When Refinement List component has Show More feature configured, new validation logic ensures correct values of Show more limit and Limit properties

• Enhance ClientUniformText component to support custom styles (UNI-9355)
• Items in releases can now be copied to other releases from the release detail view (UNI-9161)
• Unify display name checkbox label across components, entries, and blocks (UNI-9253)

Uniform packages published with version 20.63.0

• design-system package - <SegmentedControl> component got fixes:
  • prevent text wrap
  • handle scrolling
• mesh-sdk-react package - fix placeholder position for <InputVariables> component

CLI

• Add search option to canvas CLI commands

SDK

• A new package 19.149.0 was released with no breaking changes

• Nuxt and Vue packages:
  • Added support for Nuxt.js v3.17.
  • Introduced the useUniformContextualEditingState composable to help developers adapt frontend behavior based on the visual editing state in the Canvas editor. The composable can be imported from @uniformdev/canvas-vue

Package update

• Uniform packages published with version 20.16.0

• mesh-sdk-react - make getDataResource work with variables in parameter values

Bug fixes

• Fix timezone formatting and name fallback in older Chrome and Safari versions
• Fix various redirect editing edge-case issues

SDK

• A new package 19.150.0 was released with no breaking changes

• Allow to configure a/b test and personalization variant settings when they are immediate children of each other
• Discard asset parameter changes on modal close
• Added results per page to pagination on composition lists

SDK

• A new package 19.142.0 was released with no breaking changes

• Fix an entries filter UI bug where the content type filter was allowed multiple times
• Fix a UI regression on the "add project map node" screen
• Fix release failing to save when no schedule was set

• Fixed issue where binding to Uniform entry blocks from within a composition would throw an error in the API
• Fixed a bug in the Nuxt SDK with the unguarded window global use

Package update

• Uniform packages published with version 20.18.0

• Fix broken binding inside components under the Loop after deleting the corresponding data resource
• Fix broken localized fields after the invalid transition between non-localized project
• Fix nested Slot Section overrides

Improvements

• New allowBindingSearchTerm flag that enables binding of keyword search input in SearchAndFilter component
• New common property for Mesh Location metadata - dashboardOrigin
• Improve error reporting when loading data resources times out

• The issue where changing the "Visitor Distribution" values on the A/B Test component level did not correctly update the variants has been resolved.

• Fix an issue where some assets would be omitted from a composition served by the API

• Prevent overflow of Data Resource menus when no Data Resource data was rendered
• Now it is possible to add Search Parameter to Project Map nodes without default values

SDK

• A new package 19.142.1 was released with no breaking changes

• Improve the responsiveness of the Canvas editor
• Fix an issue where the "Take me back" banner inside Canvas preview was shown unnecessarily

Improvements

• Add the option to skip the preflight modal if preflight checks pass

• Fix an issue where the A/B Test component nested within the Personalization component was not available in Preview
• Disable auto-scrolling in the preview panel

• We've made some optimizations to the Canvas and Route APIs. As a result, customers are experiencing an average reduction of 25% in response time.

Bug fixes

• In some cases, users were previously unable to immediately launch a release. This issue has now been resolved.
• Assets: Fixed issue where users with “Editor” role were not able to upload the first asset to a project

• Fixed bug with sdk.currentWindow?.updateHeight() breaking when passing same height second time in a row.

Improvements

• Custom permissions for individual users are now deprecated. Centralised role management is in development which will provide more control over permissions located in one place.

Package update

• Uniform packages published with version 20.14.2

• Data resource errors now include an optional statusCode property that contains the HTTP status code from the failed fetch (UNI-9158)

// Filter for errors that have status codes
const fetchErrors = issues.filter(
  (i): i is DataResourceIssue =>
    i.type === "data" && typeof i.statusCode === "number"
);

// Filter for specific status codes (e.g., rate limits)
const rateLimitErrors = fetchErrors.filter(i => i.statusCode === 429);

This addresses the need to handle errors beyond simple message filtering, particularly for rate limits (429) and other HTTP status codes.

• Custom edgehancers can now report HTTP status codes when registering errors via the mesh-edgehancer-sdk:

// Custom edgehancers can include statusCode in error objects
return {
  errors: [
    {
      message: "Failed to fetch data",
      statusCode: 404
    }
  ]
};

The statusCode field is automatically validated and passed through to the final error response.

• Replaced ariakit with base-ui component library within the uniform design system (the replacement is backwards-compatible)

Improvements:

• Improved validation clarity of the locale definitions management screen (UNI-9265)

Bug fixes:

• Pattern-derived components now properly show Personalize This and A/B Test This options in the composition editor preview highlighter, and variant menu items display both the variant name and component title for better clarity. (UNI-5842)
• Fixed the "Open a different composition" button being cut off in the header when the Scout sidebar is pinned. (UNI-9268)
• Slot's allowedComponents list now allows IDs of up to 100 characters, matching the maximum length allowed for component public IDs (UNI-6697)

Uniform packages published with version 20.61.1

• Fix for unintentional Link Parameter unbinding in Canvas Editor.
• Fix visibility of the A/B Test when using Next.js app router / React Server Component in developer mode.

Improvements

• Avoid resolving Contentful references deeper than specified by include setting.
• New ability to require consent for personalization to run. This new option is available when you are configuring an instance of Context object. SetrequireConsentForPersonalization to true if you want personalization to depend on consent value (default false). Update @uniformdev npm packages to 19.202.0 to get this new feature.

• Canvas Editor - Small UI bug with vertical separator line in Parameters panel (UNI-8398)

Package update

Uniform packages published with version 20.42.1

• The Canvas Next RSC package received the following improvements in v19.205.0:
  • Improved the <DefaultNotImplementedComponent /> component to provide more useful information inside Canvas editor.
  • The playground will be used to try to preview compositions without a project map node. This behavior can be changed using the resolveFullPath property of createPreviewGETRouteHandler.

• <MediaCard/> component was marked deprecated in favour of <ObjectGridItem/>
• Misc improvements for <StatusBullet/> and <Menu/> components

• Canvas Next RSC package: Added releases support for preview
• CLI: More verbose networking error messages
• Context packages: added experimental cookies serialization support

• API - /v1/entity-releases API now supports filtering by release state(s)
• CLI - Uniform CLI scaffolding commands (new, new-integration, ai rules install) are now natively aware of the EU version of Uniform

Bug fixes:

• Canvas - Global query string values on link parameter values are now computed properly.

Package update

Uniform packages published with version 20.43.0

• Fix initial filters not being set correctly on data resource query filter types
• Launching editions on releases is improved

Improvements

• Improved search index and sorting performance

You can now use Scout directly from the “Insert component” dialog. Just describe what you want in natural language, whether it’s a simple component or a complex, nested structure with some specific content, and Scout will build it for you at your selected location. You can also upload files to provide content or instructions for Scout to use. After insertion, you can continue refining your new components with Scout in the chat.

UI update: Built-in components now in “Built-in containers” category

Built-in components for A/B tests, Personalization, Loops, and Localization now appear in a new “Built-in containers” category at the bottom of the “Insert component” dialog. This update puts your project’s components front and center, while keeping built-ins easy to find for experience architects.

Improvements:

• Allow opening block drawer when read-only (UNI-7708)

Bug Fixes:

• One can now choose 'Not set' when setting a preview value or link param value for query strings with predefined options (dropdown list) (UNI-8296)
• Link parameter URLs shown in the editor UI will correctly reflect global query strings when used (UNI-8296)

Package update

Uniform packages published with version 20.41.0

• New version of Nuxt 3 packages with improvements to preview functionality and support for latest contextual editing features.
• Support of latest Nuxt 3.14.159 and 3.5.12.
• Our Nuxt starter kit was updated with the latest packages here.

Bug fixes

• Contentful integration fixes in content resolution.
• Fix for usage tracking on composition and entry patterns.

• CLI: Fix the order of operations during the sync command (deletes are now processed before writes)
• CLI: Fix the What-If functionality for the publish and unpublish commands

• Added consent toggling
• Added preview mode flag allowing to resolve if you are in the active editing mode or preview mode.

• Fix localization of references

• Workflows - In workflows, a UI regression prevented authors with stage transition permissions from executing a transition unless they also had stage write permissions. It is not intended that stage write permissions are required to execute a transition. (UNI-8089)
• Search - Fixed an issue where content types with a large number of entries would not be indexed properly.
• Uniform MCP - Fixed an issue where the MCP server would fail to start.
• Next.js App Router SDK - Auto-generated cache tags are now ASCII-encodes to ensure compatibility with Vercel

Package update

Uniform packages published with version 20.39.0

• Exclude blocks from Contextual Editing inside Preview
• Fix for Components Usage tracking

• Allow Custom Edgehancers to register data issues related to unpublished content.
• Improved performance tracking of Custom Edgehancers.
• CLI: Better support for --verbose and --what-if flags.

Improvements

• Performance improvements to content indexing.

• Assets - imageFrom utility now supports images served from the EU data residency (UNI-8254)

Package update

Uniform packages published with version 20.39.1

• Simplify email validation for user registration process

• Assets - Asset parameter dialog menus no correctly show on top of the dialog (UNI-8253)
• API - Fixed a bug where requests were not rate-limited properly, leading to a decrease in API performance

• Webhook events for compositions, entries, redirects and project map nodes now include the user details of who triggered the event, improving traceability for actions.

• Fixed placeholders and a preview mode regression in the RSC SDK

• Canvas - Usability improvements were made to the key/value input used when setting up static lists on dropdown parameters, quirks, and query string parameters. It is now explicitly documented that the enter key inserts a new row after the current one, and it also accepts pastes of multi-line text values to add multiple values at the same time (optionally comma-delimited within a line to set separate names and values).

• Canvas Editor - Fixed issue with broken preview not working in development mode. (UNI-8290)
• Search - Fixed API exception when filtering by content type field in projects with 50+ locales (UNI-7243)

Improvements

• Search - Content indexing performance improvements (UNI-8285)
• Improved Empty Locale Handling by adding filtering to remove empty strings from parsed locale candidates. This prevents issues when locale input contains trailing commas, double commas, or whitespace-only entries.

Package update

Uniform packages published with version 20.40.0

• Better error handling for missing bound value due to locale mismatch
• Parameter keeps its configuration when delete and added back right away

Bug fixes

• Fix Project Map tree flickering
• Fix cross-domain redirect management

• Relationships - A/B test usage is calculated correctly now (UNI-7945)
• Data Types - fixed inability to save Data Type edit form if Edge Cache is disabled (UNI-7915)
• Mesh - fixed broken Parameter Editor for mesh integrations with query parameters in base url (UNI-7952)

Improvements

• Canvas - allows to bind "single select" field types in Uniform Content data resources (UNI-7815)

Package update

Uniform packages published with version 20.34.1

• Performance improvements around edge workers internal logging
• Add last modified date to project map composition data
• Simplify marking fields/parameters as Display Name or Thumbnail
• Simplify creating Key/Value options in parameter/field settings

Bug fixes

• Show empty teams in Teams/Projects navigation menu
• Fix for new entry slug value not updating when modifying
• Hide Slug editor from Entry Editor if it was disabled in Content Type settings
• Auto-refresh compositions list after unpublishing a composition inline
• Fixes for responsiveness of SearchAndFilter inputs

CLI - Added AI assistant helper

• New commands:
  • uniform ai mcp install — Install and configure Model Context Protocol (MCP) servers.
  • uniform ai rules install — Install AI-specific coding rules.
  • uniform ai rules list — List available AI rules.
• Supported tools: Cursor, Claude Desktop, and other MCP-compatible AI agents.
• This enables you to install the Uniform MCP server, connect it to your Uniform project, and install rules and best practices for AI-agent awareness.

Webhooks - Added Email notifications for webhooks.

• You can now add an email address to a webhook’s configuration to receive notifications for:
  • Endpoint disabled — Sent when an endpoint is automatically disabled after repeated delivery failures for 5 consecutive days.
  • Delivery attempts exhausted — Sent when a message fails after all retry attempts have been exhausted.

Improvements

• The unpublished data resources toggle in the composition/entry editor will now only appear if there is a data resource on the composition, entry, or pattern that supports unpublished content. (UNI-7835)
• Improved the empty state message on the Components list page to correctly distinguish between a truly empty project and filtered results that yield no matches. Users will now see the appropriate "Create your first component" message or "No results match your current criteria" based on the project's content and active filters. (UNI-7885)

• Fix locale mapping for Uniform Content in Uniform Edge API

• CLI - Improve uniform new error message for insufficient permissions (UNI-5763)

Improvements

• Canvas - Parameters and fields on patterns that are overridable have validation errors downgraded to warnings. This makes it possible to use required fields on patterns without providing a default value! (UNI-7966)
• Canvas - Dragging to move components into empty slot sections is now easier (UNI-5221)

Package update

Uniform packages published with version 20.36.0

• Canvas Editor - Fixed an issue where the browser tab title for component pattern pages incorrectly displayed "Edit Composition [name]". It now correctly shows "Edit Component pattern [name]" or "Edit Composition pattern [name]" as appropriate. (UNI-5747)
• Context UI - long value dimension names now truncate with a tooltip (UNI-7828, UNI-6834)

Improvements

• Canvas Editor - The editions selector menu is hidden if there are no editions yet (UNI-7838)
• Canvas Editor - Required fields and parameters now have a * icon next to their name for easy identification (UNI-7831)
• Canvas Editor - Icons on fields and parameters, such as localization, AI, and conditional values, are hidden until hovered or the field is focused (UNI-7834)
• Canvas Editor - The publishing status is an icon with more information in a popover, the label was removed. The publishing status is also available in the save and publish menu. (UNI-7840, UNI-7839)
• Canvas Editor - The toggle for fetching unpublished data resources data is no longer shown unless there is a data resource present that actually supports the feature

Package update

Uniform packages published with version 20.36.1

• Context - changing dimension in personalization criteria keeps operator and value (UNI-7862)
• Design System - Button with menu component icon does not shrinking anymore (UNI-7865)
• NextJS App Router - Resolved a display issue causing text parameters to look editable outside the canvas editor (UNI-7878)

Package update

Uniform packages published with version 20.32.2

• Visibility Controls - When using dynamic tokens as a criteria for component visibility or conditional values, the value shown is now the path to the dynamic token instead of the current value of the token. We still show the current value when previewing the evaluation result. (UNI-8029)
• Entry Preview - When opening an entry preview, showing unpublished entries data is automatically enabled (fixed regression). (UNI-8026)
• Parameter Editor - Add conditional rendering for editor settings and conditions & localisation tabs within the parameter edit form. (UNI-8045)

• Support binding of a whole value for Link and Block fields when binding Entries to a Composition

• Fixed bug with processing emotion style tags in edge worker
• Composition overrides were suppressing composition pattern overrides, but this has now been fixed.

• Asset Library now supports more file types: .srt, .vtt (UNI-7886)

• Access and change between all releases in a project with ease,
• Identify which releases the current composition, pattern or entry has already been copied to or modified within,
• and, check the status for releases at a glance.

To learn more, check out the video above!

Features

• Rework the structure of asset parameter and API

Bug Fixes

• Add public_id to prompts
• Large text in AI current value, result not visible

Shipped 19.79.0 platform and packages 

Features:

• Pass max assets amount config to external asset param location

Bug fixes and other tasks:

• Fix config for blocks to prevent min max from being more less than each other
• Fix and improve the resizing of editor panels

By using releases, editors will be able to;

• Build and publish content in a preview environment away from production to review multiple content edits at the same time.
• Create and schedule multiple iterations of content ahead of time, to support regularly updating content - such as a daily promotion that appears on a home page.
• Launch content in bulk across multiple pages and entities, allowing for large campaigns or broad-spanning content releases to be handled in a single place.

The releases feature is included for all Enterprise-level projects, and will be provided in a limited capability to non-Enterprise projects.

To learn more about this feature, check out the video above, or see our documentation.

Note; new release-specific permissions have been added which will be off by default for existing roles. To enable this feature for non-admin users, simply add release permissions to the applicable roles in your team.

This improves content aggregation based on fields of entries where the data is sourced from a third party system like a PIM or external CMS.

a nice quality-of-life update to the UI that is used to manage the overrides for patterns. The new UI provides a sleeker and simplified design, trading out radio buttons for checkboxes to make it easier to manage your parameter and variant overrides in a more manageable way.

Before this change, users were unable to add additional child components to a slot within an instance of a Component Pattern.

With this update, Component Patterns are receiving a significant enhancement - the introduction of Slot Sections.

This feature allows users to define special areas - so called Slot Sections - within slots of Component Patterns, with the option to specify constraints on the type and quantity of components that can be placed within them. This empowers the creation of reusable container components, greatly enhancing flexibility for Component Patterns.

Want to include additional buttons or links as CTAs within a Hero component, or incorporate other components within it? Slot Sections make it effortless. With this update, assembling components from atomic elements and authoring new ones is now easier than ever, all without the need for coding.

Learn more about Slot Sections in our documentation

Support for image assets

• Embed images directly in your Rich Text parameter: Insert images within the editor in a few clicks.
• Composable: Source images from your asset library, DAM integrations or external URLs.
• Copy & paste support: Easily upload and embed images from documents, websites or your file system by simply copy and pasting them
• Flexible rendering: Customize the styling and rendering of images in your applications by using the updated Rich Text SDK ( >=19.187.0).

Support for tables

Manage and present tabular data in Rich text parameters and fields:

• Create tables directly in your Rich Text parameter: Insert and manage tables within the editor in a few clicks.
• Copy tables from external sources: Seamlessly paste tables from websites, documents, and spreadsheets.
• Configure row and column headers: Easily designate headers for improved accessibility and clarity.
• Flexible rendering: Customize the styling and rendering of tables in your applications by using the updated Rich Text SDK ( >=19.181.1).
• Rich cell content: Insert any supported content and formatting within table cells, including text, lists, links, code, or quotes.

Note: For existing Rich text parameters you will need to allow assets and tables to be used. Learn more about how to use Rich text in our documentation.

• You can now get information about the usage of patterns across your Uniform project

Bugfixes

• Fixed issue where a prompt with an empty name could be saved

Change Overview: To enhance the stability, accuracy, and overall developer experience, we will discontinue this type-coercion feature starting June 24th, 2024. This adjustment constitutes a potentially breaking change for any integrations that do not adhere strictly to our API schema and rely on this previously undocumented flexibility. Note that the coercion will continue functioning for parameters passed as part of the URL.

Implications of the Change:

1. Read Operations: If you are using the Uniform SDK/APIs solely for reading data from the Uniform platform, no action is required on your part. There will be no changes affecting read operations.
2. Write Operations with SDKs: If you are utilizing our SDKs to write data, rest assured that no action is required. Our TypeScript SDKs have always enforced correct data types, and your existing implementations will continue to function seamlessly.
3. Direct API Writes: If you are directly interfacing with our APIs to write data, you may be impacted by this change. It is crucial to ensure that the data you send strictly conforms to our published schema, which is available at Uniform API Schema.

Example of Change:

Current API Call (Accepted until June 24th, 2024):

{
    "projectId": "{{Project ID}}",
    "categories": [
        {
            "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "name": "Some category",
            "order": "10" // Currently accepts a string that represents an integer
        }
    ]
}

Required API Call Post-Change:

{
    "projectId": "{{Project ID}}",
    "categories": [
        {
            "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "name": "Some category",
            "order": 10 // Strictly requires an integer per schema definition
        }
    ]
}

A new parameter type for components and a new field type on entries are now available.

Like components, blocks are stored within an entry or component instance on a composition and are not individually addressable via UI or API.

This 6th generation of CSK is a complete rewrite of the previous version and includes a number of new features and improvements. It is based on are more minimalistic approach and includes only the most essential components and features:

• This version is built specifically for Next.js 15 (and exclusively available in the App Router flavor) and React 19, leveraging the latest Uniform SDK v20+, enabled for all the latest Uniform DXP features!
• Much more lightweight, minimalistic and simplified approach:
  • zero external dependencies besides @uniformdev, minimum distractions - essentials only in the core version.
  • zero components added to the codebaseby default, can add components into your codebase with npm run component:extract and customize how you see fit
• Revamped theme management system based on a new Design Extensions integration that supports design tokens
• More atomic components supporting built with patterns leaning on the authorable components paradigm
• Optimized for great performance out of the box
  

  

• Internationalization / localization ready (with a more advanced localization recipe coming soon)
• Removed daisyui and many other non-essential dependencies
• Included standard sitemap implementation Server-side rendering by default. Static site generation can be enabled on top. Dev Experience updates: component:scaffold and component:extract flows, watch mode for design extension update sync and a developer config for content sync that scopes the operation to developer artifacts only.

Check out the documentation on how to get started.

Past release information will continue to be available on the Uniform website. This changelog will contain updates after November 15, 2023.

This capability co-exists with your existing analytics tools.

Key differentiators

• Fully integrated with the Uniform visual workspace
• See analytics in context of where content and experiences are managed visually
• Full control over the data collection (region and data center)
• Anonymized data collection
• Real-time data access, see results in seconds
• Ad blockers friendly
• No tracking pixels
• No cookies

Learn more in our docs.

All MCP enhancements require both upgrading your uniform-mcp npm package to the latest version, as well as updating your Uniform AI Rules

• Expanded Editing Capabilities:
  • Can now create and edit compositions, entries, and their respective patterns.
  • Can insert, move, and duplicate pattern instances in slots on compositions and patterns.
  • Can rename compositions, entries, and patterns.
  • Can change the slug of entries.
  • Can update the description of patterns.
  • Supports editing and resetting overrides on pattern instances
  • Smarter handling of localized property values
• Locale Management:
  • List locales registered with Uniform.
  • Can enable/disable locales on compositions, entries, and patterns.
• Search Enhancements:
  • More accurate and intelligent search across patterns, compositions, and entries using prose as search expressions, for example find compositions updated this week or which products cost more than 25 or find unpublished hero patterns
• Metadata:
  • MCP can now report the connected Uniform team, project, and user.

Component registration made simple

Describe your frontend components in natural language and automatically:

• Generate Uniform component definitions from existing component props
• Create proper parameter configurations with correct field types
• Eliminate manual mapping between code and Uniform components
• Register entire component libraries without repetitive dashboard work

Content modeling from your IDE

The MCP server also enables:

• Creating content types with custom field definitions
• Managing your experience model without leaving your development environment

Component patterns

Building component patterns for reusable layouts. Simply describe what you want to create and let your AI editor handle the Uniform configuration.

How to get started

Ready to try the MCP server? Send us a request for developer preview, then check out the setup guide and share your feedback in our developer community.

Features:

• UTM Mapper support

 Fixes:

• Fixed incorrect detection of whether to publish a composition/entry
• Fixed copying of Uniform Content data sources and types
• Fixed copying of files and assets

If you're not seeing version 0.0.26 in the extension popup, you can force-update the extension from the "Manage extension" screen.

Selecting a component in the structure panel will no longer auto-expand its child components. To view the children of a selected component, click the chevron icon to the left of the component.

This change reduces unnecessary expansions of child component, making it easier for users to navigate and manage complex component structures efficiently.

Improved Hierarchy

The header of Canvas has been re-arranged to make it clear that switching releases will impact everything within the editor. This also places in a similar location to where you’ll find releases outside of Canvas.

The visual preview is really the star of our visual preview, so with this refresh we’ve popped it out with some delicious drop shadows and given it the visual prominence it deserves.

These changes to hierarchy also support upcoming features for visual preview and an even more powerful localization feature. Stay tuned!

New global navigation

The Canvas editor is no longer navigating into a cul-de-sac. The familiar back button is still present (and you can still use your browser’s back button), but now we have a nav menu. To save you a few clicks, this single hamburger menu provides direct access anywhere within the Experience section of Uniform and top-level access to Optimization, integrations, and settings.

This global header now also makes it clearer when what type of object you’re working on. No longer will there be a pause to ask: “is this a component pattern or a composition pattern?” In fact, you’ll see these improvements for all Canvas editors including composition defaults, workflows, and entries.

Re-organized project map connection

We improved the UI to attach a composition to a project map node. Any dynamic inputs in the path will be resolved using the current preview values.

Dynamic tokens that are available to use are listed separately, alongside the current locale. This is because dynamic tokens will soon include more than just project map dynamic nodes and query strings! As before, clicking on any chip will allow you to edit the preview values for all of them.

• Fully customisable stages – All stages can be customised so that you can tailor your content workflow to the needs of your team.
• Stage-based permissions – The ability to lock editing and publishing for specific user roles during certain stages helps to prevent content from being published prematurely or without review.
• Status at-a-glance – workflow states help determine where a composition, entry or pattern is in the content lifecycle, making it easier to stay on top of what needs to be taken care of next.

• Next.js app router SDK: allow cookieAttributes to be set on client context transition store
• Vue SDK: improved support for preview, pattern preview and Rich Text Editor parameter type handling

Bug fixes

• Changes to custom integration manifest are applied without reloading the application