You can check blog articles order by publish date.
The Sitecore command line interface is provided as a command line tool that allows command line control of the Sitecore environment. In this article, we will review the procedure for using this tool to perform an import using sample data.
Previously, we installed Sitecore Management Services. Now, we will install the Sitecore Headless Services module. Additionally, since the SXA module is included by default and won't be used, we will remove it.
To enable working with custom images using the Sitecore CLI, we need to add Sitecore Management Services. Without this on the CM server, the CLI won't function. This guide covers container setup, while for other environments, please install via package.
We have been able to create a custom image, but the administration screen, etc., is still in English. This section introduces the procedure for adding Japanese resources and settings so that Japanese language can be handled.
Since we were able to start using the sample custom image, we will now introduce some unnecessary parts and points that need to be changed for future use.
So far, we have been testing the operation by launching a sample Docker image, but in reality, we will be creating an image that contains the modules we will need. This time, we will create a custom image that you want to use yourself from the sample.
In this article, we'll explore integrating Figma, a free browser-based design tool, with Sitecore Headless. We'll create basic components in Figma and demonstrate how to fetch data via GraphQL and reflect it in the design.
Sitecore XP's personalization feature provides several rules for configuring personalization based on the history of the visitor's behavior when browsing to a page. In this article, we will explain how to configure each of these rules and how they work.
Sitecore CLI, Sitecore's command line tool, will be installed on macOS this time. This is because Sitecore CLI also runs on macOS since it is provided as a command that runs on PowerShell Core and .NET Core 3.1 base.
In the previous article, we only prepared the environment and did not start the container. This time, we will check how the container will be started by referring to the script up.ps1 to run the sample.
The demo Sitecore Helix provided by Sitecore includes a sample based on Next.js. In this article, we will show you how to run this sample. The actual container launching will be introduced in the next article.
Sitecore provides a command line tool that can be used for development efficiency and operation. In this article, we will show you how to install this tool, Sitecore CLI.