Front-end management | Uniform | Uniform platform docs

Uniform enables you to use content from Sitecore to power omnichannel digital experiences without depending on Sitecore to management the front-end. But if you already a Sitecore site, you already have a front-end. You have the following options when adopting Uniform:

Build an entirely new front-end - You are planning a new front-end and are only using content from Sitecore.
Migrating the front-end from Sitecore - You want to retain your existing front-end, but you do not want to manage it usig Sitecore presentation details.

Build new front-end#

If you are doing a site redesign, you are creating your front-end from scratch. You do not need to worry about migrating your existing Sitecore front-end. Your focus is on creating front-end components that can access content from Sitecore items.

In addition, you may create new front-end components after you have finished migrating renderings & layouts from Sitecore and need to create new front-end components.

tip

This example uses Next.js as the front-end framework, but you can use any front-end technology you want. The layout and components defined in Canvas are technology agnostic.

Create web app#

Open a command-line interface (CLI).
Enter the following commands:
Create a file named .env
Add a file .env and define the following variables:

Name	Value
`UNIFORM_API_SITENAME`	`website`
`UNIFORM_API_KEY`	Your Uniform API key. Use the same value as you configured on the Canvas Integration Service in Sitecore.
`UNIFORM_PROJECT_ID`	Your Uniform Project ID. Use the same value as you configured on the Canvas Integration Service in Sitecore.

The file will look like the following:

Add npm packages#

In order to add Uniform functionality to your web app, you must add a number of npm packages. Some of these packages are publically available and some require an npm access token.

Enter the following commands:

Add Uniform config#

You must configure Next.js to load Uniform settings when it runs.

Open the file next.config.js.
Change the contents to the following:

Create front-end component#

info

Coming soon.

Map component name to implementation#

Each component defined in Canvas has a public ID. When you defined the component in Canvas, you specified this value.

When your web app reads composition definitions from Canvas, the composition and the components that are assigned to the composition are identified using this value.

You must provide instructions to your web app on how to map the public ID to the front-end implementation of that component. In your web app, React components provide that implementation.

Create a file lib/resolveRenderer.js:

Add Uniform to page#

In Canvas you have a composition that represents the home page and describes the layout for the page. You have a number of React components that represent the implementation of those components. Now you must configure the Next.js app to use the information from the Canvas composition in order to render the page using the React components you implemented.

Add composition component#

Replace the contents of the file pages/index.jsx with the following:

About this code

The component Composition accepts props that represent the composition (which is retrieved from Canvas) and a function that resolves the React component that corresponds to the public id for a component from Canvas.

This code also adds a component to render the slot main. You defined this slot when you defined the composition component.

Retrieve the composition#

Add the following code to the top of the file pages/index.jsx:
Add the following code to the file pages/index.jsx:

Add enhancer#

When you retrieve the composition from Canvas, Sitecore item ids are included in the data. You must use an enhancer to retrieve the fields for those items.