This blog describe about Sitecore and relateted technologies
Since the demo environment at hand has the same configuration as the organization that subscribes to XM Cloud, Sitecore CDP, and Sitecore Personalize, we would like to confirm how the integration works in practice.
In this article, we will review the differences between Sitecore Cloud SDK and Sitecore Engage SDK as SDKs for integration with Sitecore Personalize.
In this article, we will check the folder settings related to placing components in Pages and Experience Editor, which are editing tools as you see them.
Sitecore Headless SXA can use Variants to switch between component rendering. In this article, we will examine the base template for creating components.
In this article, we will check the last item in the SXA Component Wizard's Behevior, the Dynamic Placeholders item.
With regard to the Component Wizard, we have reviewed the data source and the settings for creating a new item. This time, let's take a look again at the Background Image, which is a setting for Behaviors.
This time, we will check the Datasource item on the Datasource tab of the Component Wizard.
The Component Wizard has been introduced several times on this blog, and I would like to confirm the differences in the actual settings. This time, I would like to show the difference point standard and Select Page as a data source.
Yesterday, I introduced the procedure for dealing with the new repository type, and I have also published a sample code that I have applied to the sample code on my blog. In this article, I will show you how to use it.
With regard to the XM Cloud starter kit, information has emerged that it will replace the headless-first configuration. We would like to change the configuration of the repository, referring to this information.
I have previously introduced Sitecore Components, and in this article, we would like to introduce the new components and their integration with the CMS in three parts.
In sxastarter, the XM Cloud sample, a path definition is added in tsconfig.json for easy specification of frequently used paths. This time, I will use @/ for the path definition, which is my personal preference.
Showing 1 to 12 of 415 results