You can check blog articles order by publish date.
Since the Next.js template already includes a module for multilingual support, it is relatively easy to add more languages by adding settings on the Sitecore side. So this time, we would like to add Japanese resources.
Until now, Sitecore's editing environment utilized two tools: the Content Editor for an overall view and the Experience Editor for WYSIWYG editing. The new tool we're introducing, Sitecore Horizon, combines the best features of both.
In a previous blog entry, we introduced the procedure for installing the connector that integrates Sitecore's CMS with Content Hub. The new version of the connector has been released and now supports installation using the Sitecore Install Framework.
In the last issue, we created and placed a new component, but it still looks like a Tailwind CSS design with just normal HTML displayed. This time we want to change the appearance a bit and also change a few attributes of the content.
In the previous article, we organized the header and footer areas. In this article, we will create a new component for the Hero area to be used on the top page. Through this procedure, you will learn how to create a new component.
In the previous article, we implemented Tailwind CSS to the point where it can be used. This time, we will review the steps to separate the navigation code contained in the layout into separate files before using it.
The Next.js sample is configured with bootstrap as the standard CSS style sheet, and although various CSS style sheets are provided, we will switch to using Tailwind CSS.
Last year, we introduced Moosend's service on this blog. Now, it's being offered as Sitecore Send, a service tailored for businesses. In this post, we'll reintroduce the product and explain the differences between Moosend and Sitecore Send.
This time, we will change things up a bit and show you how to apply Google Tag Manager with Next.js instead of Sitecore. We will also include a test.
By installing the Headless Service for Sitecore XM, data can be retrieved using GraphQL. In this article, we will show you how the data can be retrieved.
Previously, we focused on deploying Sitecore SDK sample code. Now, we'll shift to developing within Sitecore and supplementing with code. In the latter part, we'll revisit the steps to create an empty project and progress to connecting it.
In the previous article, I deployed a Next.js sample to Sitecore and integrated Vercel for delivery. This time, to facilitate easier testing and verification, we'll introduce the steps to separate production and staging environments and test locally.