Add Japanese language resources
The XM environment is already running, but the admin interface is in the default English. This time, we'll introduce the steps to add Japanese language resources, enabling the use of Japanese in the admin interface.
Docker is an open platform for developing, shipping, and running applications.
The XM environment is already running, but the admin interface is in the default English. This time, we'll introduce the steps to add Japanese language resources, enabling the use of Japanese in the admin interface.
In the previous article, we were able to launch an instance of XM1. In this article, we will configure additional settings to make the Sitecore Experience Accelerator module available to the container, which is necessary for adding Next.js projects.
While there's plenty of Sitecore information available in Japanese, knowing where to start can be challenging. For our first post of the year, we'll show you how to quickly create a new project.
I've been working with XM Cloud in a SaaS environment. For development, I need a local setup. A GitHub repository offers a Docker environment for this purpose, so I plan to use it to run XM Cloud locally.
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.
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 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.
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.
Previously, we set up the server, but the key is to run the container locally. Let's organize the steps we've taken so far to prepare an environment where Docker-based Sitecore can run on our local machine.
I haven't posted on my blog for about a month, as I've been working on a new series to summarize previous tips. In this series, we'll build an environment to run Sitecore Headless locally, reflect changes on the server, and deploy it to a web server.