Learn
Learn about Uniform
Uniform enables you to build and maintain composable systems without having to build and maintain all the connections between those systems yourself.
Composability#
Headless systems are designed to connect with other systems, integration is expected. However, this just means systems are composable. Composability requires an architecture that facilitates change with ease. Products must not be so tightly coupled that you're unable to update the products in your architecture. Composability means no one application is irreplaceable or dominant.
This is what Uniform is all about: making it possible for you to create a composable architecture without having to take on the responsibility to connect all of your products yourself.
Orchestration#
A composable architecture is more than just a bunch of different products that are integrated in some way. Those systems have to work together like a single system. A key part of "working together" involves the ability for the system itself to manage aspects of how the component products interact with each other.
Orchestration is the ability of a system to manage, guide, or control the flow of data or processes that span multiple products. Uniform, as the foundation for a composable architecture, provides orchestration across the products that make up the architecture.
Examples of orchestration in Uniform include:
- Making content and data from one product available to all other products in the tech stack, and doing it in a way that's appropriate for each of the target products.
- Enabling omni-channel digital experience creation and deployment.
What you can do with Uniform#
Uniform is comprised of these key features to provide the tools marketers and developers need to do their best work.
Uniform Canvas
Business users create personalized digital experiences using your design system.
Uniform Context
Understand your visitors' interests & intents and deliver personalized experiences at the edge.
Uniform Mesh
Unlock content and data from all of your composable, non-composable, and legacy systems.
Uniform makes life easier for everyone involved with creating and maintaining digital experiences:
Role | Use cases |
---|---|
Architect |
|
Designer |
|
Front-end developer |
|
IT professional |
|
Marketer |
|
Merchandiser |
|
Navigating the docs#
Our documentation is organized into the following categories:
Section | Description |
---|---|
Get started | Step-by-step guides to get developers incorporating Uniform into your applications as quickly as possible. |
Learn | This section! This covers what you can do with Uniform. This is where you will find the information you need to fully understand what Uniform is and how it works. |
Guides | Instructions on how to do things with Uniform. Unlike the tutorials, which take you through very specific scenarios, guides are more generalized. For example, a tutorial might cover how to add personalization to a product detail page in a web shop, where a guide might cover how to add personalization to a component using Uniform. |
Integrations | Details about the various connectors Uniform offers. |