Create your first Sitecore Next.js Component

Create your first Sitecore Next.js Component

This will guide you in creating your first Sitecore component using Next.js. The approach we will be using is the Sitecore-first development workflow (opens in a new tab). You will learn how to create a json rendering, add placeholder settings, and create the next.js component attached to it.

If you do not have a local environment yet, see prerequisites and installing a Sitecore environment.


This guide assumes you've installed and configured your Sitecore environment with xmnextjs as the site name.

Log into Sitecore

First log onto your Content Management environment https://cm.xmnextjs.localhost/sitecore using user name: admin and the password you entered on step 4.1 of installing Sitecore.

Once you've logged on, you will see the launchpad. Click on the Content Editor.

Content Editor

Create a rendering

  1. Navigate to /sitecore/layout/Renderings/Feature
  2. Create a rendering folder
    1. Right click, insert, and select Rendering Folder
    2. Name it Article
  3. Create a json rendering
    1. Navigate to the Article folder you created
    2. Right click, insert, and select Json Rendering
    3. Name the rendering Article as well

At this point you should have something that looks like the below. Mentally note that the component name is also Article as specified under the Component Name field Article Json Rendering in Sitecore

Add rendering to Placeholder Settings

The Placeholder Settings is a place where you specify what renderings content editors are allowed to place in a placeholder. We will add our newly created Article to the list of renderings that the Main placeholder is allowed to have.

  1. Navigate to /sitecore/layout/Placeholder Settings/Project/xmnextjs/jss-main.
    Note: you actually have to click on the Main item in Sitecore. This is because even though the item name is jss-main, the Display Name is Main. Placeholder Settings
  2. Under Allowed Controls click edit
  3. Navigate to the Article component, and double click to select (alternatively, click the right arrow next to Selected) Placeholder Settings - Allow article
  4. Make sure Article is on the right side under Selected
  5. Click OK
  6. You will see that Article is now in the Allowed Controls field
  7. On the main ribbon, click Save to save the Main Placeholder Setting item.

Add rendering to a page

Now that you have created a rendering and specified where on the page the rendering are allowed to be placed in, let's add it to an actual page. We will add the rendering to the home page.

  1. Navigate to /sitecore/content/XmNextJs/home
  2. Make sure home item is selected. On the main ribbon, Click Presentation > Details Presentation Details
  3. Click on Final Layout
  4. We see that ContentBlock is the only rendering currently on the home page Presentation Details - edit
  5. Click edit
  6. Click Controls, then click Add
  7. Navigate to Renderings/Feature/Article and select Article
  8. Under "Add to Placeholder" enter jss-main. This was the placeholder that we allowed our rendering to be placed in. jss-main is also considered the placeholder key. Presentation Details - add rendering
  9. Click Select
  10. Click Move Up so that Article is now above ContentBlock and is the first component on the home page Presentation Details - move rendering up
  11. Click OK, then Click OK to close all the dialogs.
  12. Let's view our homepage
  13. On the main ribbon, click Publish > Experience Editor. The Experience Editor is where we can preview and edit how our page looks.
  14. In the Experience Editor, we see a warning. This is because we have not created our React/Next.js component that is tied to this rendering yet. Experience editor - missing component

Create the Next.js component

  1. Open Visual Studio Code
  2. Under ./rendering/src/components, create a Feature folder, and under that create an Article folder.
  3. Create a file and name it Article.tsx Visual Studio - article.tsx
  4. Add code. Notice that the component name must match the Component Name field in Sitecore.
const Article = (): JSX.Element => (
        <h1>My first article</h1>
        <div>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</div>
export default Article

Go back to the Experience Editor and we see that our component has rendered! Ignore the "Hello World" which was part of a previous lesson. Experience Editor - article rendered.tsx

Publish changes in Sitecore

Let's visit our rendering host site: https://www.xmnextjs.localhost/ (opens in a new tab). Notice that we do not see our component. This is because we have been working under the master database in Sitecore whereas the rendering host site is connected to the web database. The Experience Editor provides a preview of our site.

To publish our site:

  1. In the Content editor, main ribbon, Publish > Publish drop down > Publish Site
  2. Select Smart Publish and all languages
  3. Click Publish

On a live site, the "Publish Site" option should rarely be used and "Publish Item" should be used instead. This is to prevent accidentally publishing content that an editor isn't ready to share to visitors.


We created a Sitecore rendering, edit the placeholder settings to allow our new rendering to be added, added the rendering to a page, created the corresponding Next.js component and publish the site.

Our component currently only has hardcoded content, which isn't useful to a content editor. In our next lesson, we will go over how to make the component content-editable.


Knowledge check:

  1. What is a rendering?
  2. What is a placeholder?
  3. How do we restrict what renderings are allowed in a placeholder?
  4. What is a placeholder key?
  5. How do we add a rendering to a page?
  6. What does a rendering's component must match to?
  7. Why do we have to publish changes in Sitecore?