Couple weeks ago I was psyched to start a series on our first hand experience dealing with Coveo for Sitecore on a multi-tenant/multi-site Sitecore instance. Check out my first two posts below:
Link Manager Gotcha
Get Your Links right
Now, last, but, not least when you have such huge instance of Sitecore, you are bent to have things you would want to localize due to multiple languages you are supporting. I usually see the solution in two folds.
- Coveo OOTB component localization
- Custom string localization – Like Facets or any strings on your search listing card that are computed field for instance.
The first one is quite simple and easy to do as Coveo carries responsibility OOTB to load most close culture based on context language. If you go to viewsource on your search page, you will see that Coveo has already done some magic for you. It loads the culture *.js file based on your context language. This happens right the view based on below line of code on Coveo Search View.
<script type="text/javascript" src="/Coveo/js/cultures/@(Model.CultureName).js"></script>
That should take care of your result summary on left top corner above your results. For your sorting components which you may have added using your DateSortView or RelevancySortView, to localize the sorting header such as “Relevancy” or “Date” in context language, Coveo looks for special data attribute on HTML called ‘data-caption’ and if your HTML element for your facet has this attribute loaded with your title and if that is a existing key on locales dictionary object of your interested culture/language then it is respected and corresponding localized string is shown on your page.
Now, for the second fold, if you would like to localize your Facet values, Headers, etc., There are few things to consider/answer – Do you show just one language content on your search page per site? If you are – Life is simple, just ensure you have localized content loaded on your Facet field. If your facet is based on computed field, ensure you are loading language specific value based on currently indexed item language. For your facet header to be localized, you have couple of options here as well, you can either read it from your localized dictionary on Sitecore if you have one, if not, load up your JS localize dictionary with new values as noted in the link below.
Now, the problem actually happens when you have more than one language content show up on your search page, in that case, you will have an issue with mixed values which obviously is not UX friendly. You can see a good solution and huddle between me and my favorite Sitecore MVP and Coveo champ below(@jflh ). 🙂
This is the last piece of this series and I am sure there will be more to come, this one is near and dear to my heart and the amount of learning and information I gathered through this Implementation is priceless. Although, Coveo and Sitecore never fail to amaze me, there is more room to learn and grow with these products every single day. 😉
Happy Coveo for sitecore implementation to every one!
Some helpful links:
https://developers.coveo.com/display/public/JsSearch/Localization