You can check blog articles order by publish date.
We have created the project multiple times so far, but it is tedious to perform the same thing each time. Therefore, we will introduce a procedure to start the environment without the previous steps.
Regarding the test environment setup, we've previously provided instructions to manually enter certain configurations. To improve usability, we'll now automate this process by consolidating settings into a .env file.
The project already has a headless testing environment set up. In this and the next session, we'll clean up and remove unnecessary parts. Since we're now running headless, we'll start by deleting the CD server configuration.
Last time, we launched a container based on Node.js and started Next.js within it, displaying pages by fetching data from Sitecore. This time, we'll progress to connecting Sitecore to the Node.js container and getting the Experience Editor up and running.
On the server, Vercel is used for page editing and verification, but this functionality is missing in the local container environment. This time, we'll add a Node.js container to replicate the Vercel functionality locally.
In the last issue we were able to deploy a new site in Vercel. We will proceed to use this instance to be able to edit pages in the Experience Editor.
We would like to deploy the web site we have created so far to Vercel. We will show you how to deploy the sample data to the server that was set up at the beginning of this series, and how to deploy it to Vercel.
In the previous session, we prepared a Next.js template. Last time, we introduced the steps to import items into Sitecore to use this template. Now, we'll modify the Next.js settings to reference Sitecore items and display the pages.
Previously, we added the Next.js template to the project, but at this stage Sitecore has no data, so we get an error. Therefore, we would like to import the sample data using Sitecore CLI.
The environment we've set up in four parts lacks a Next.js project. We'll add a sample site by integrating the code into the project. This process will be introduced in two steps. In this session, we'll get the Next.js sample running.
After setting up the container environment, the admin interface is still in English. This time, we'll introduce the process to switch it to Japanese. We'll demonstrate how to deploy resources by copying files when creating the Docker image.
To align the container environment with the server, we'll ensure all necessary modules are available in Docker. The current Docker container already has SXA and Horizon configured, so we'll install any missing components as needed.