Change the stylesheet for Preview Search in Sitecore Search
In the last issue, we applied Tailwind.css to make the page a little easier to read, and this time we will show you how to use it in the Preview Search widget as well.
You can check blog articles order by publish date.
In the last issue, we applied Tailwind.css to make the page a little easier to read, and this time we will show you how to use it in the Preview Search widget as well.
As for the Sitecore Search sample, we have no control over the sample code or look and feel yet. In this article, we will modify this project to make use of Tailwind.css and NextUI.
In the previous article, we prepared only the language switching box so that you can add the Sitecore Search widget. This time, we would like to add the widget and display the search results.
Until now, the blog has used the Sitecore Search SDK to display search results. In this article, we will show you how it actually works by adding a widget to the plain Next.js environment.
This time we will add a header and footer to the Next.js application. No external integration is included this time.
You can switch between light and dark modes on the website. I personally use the dark mode. In this article, I will confirm the procedure to implement this in NextUI.
The sample we have been running so far had no minimal design and only displayed text. In order to make it look a little nicer, we are going to make NextUI available in the project.
Until now, the Search Starter Kit has been used to create the search page, but now it is possible to display the page in Japanese simply by changing a few items. This time, we will translate some items.
As we have shown in our blog, attributes can be set with JavaScript during crawling. In this article, we will show you how to actually check the facets in action and increase the number of attributes.
Sitecore Search can search for documents in addition to HTML. In this article, we will show you how to target PDF files.
In the last issue, we proceeded to create URL-based IDs with respect to content. This time, we will remove the locale part and introduce the part where we will use the multilingual crawling functionality.
You can create a source in the form of a search result on a multilingual site that has information about the different languages of a single piece of content. We will introduce this procedure in two parts.