by Kollectify on Oct 01 2020
Ready for a totally custom approach to your on-site search experience?
In today’s e-commerce landscape, and especially with the increasing popularity of headless integrations and PWAs, there’s an uptick in diversity of how search results should look, feel and function.
This short article highlights some of the benefits this new library has to offer.
1. Easier Customizations
Wouldn’t it be great if you could skip the back and forth of requests to the Klevu Support team when making customizations to the look and feel of your store?
Klevu’s powerful AI will continue to ensure your pages remain perfectly (and automatically) merchandised, but you retain control over how your customers interact with the user interface of your store, as you finetune how it looks, feels and functions.
2. Faster Customizations
Waiting for the Klevu Support team to apply requested customizations to your store’s frontend? That’s now a thing of the past.
From minor layout tweaks to A/B testing major changes, your own team retains full control without the need to involve Klevu in those discussions or implementations.
3. Access to a Rich Set of Resources
Of course, we’re still here to help! While creating this community-driven, open-source library we wanted to give your developers access to a really valuable and flexible set of resources.
A repository of examples and tutorials is available to give your developers a head start. We created a Demo Store to showcase some of this functionality, so you can see it in action and even download the source code.
In case your developers get stuck or need some guidance, we created a Community Forum for their technical implementation questions. This is regularly monitored by our own developers, who are on standby to provide helpful code samples and suggestions.
And we’re not stopping there. We will continue to grow these areas, adding more tutorials and showcases to provide you with inspiration for improving the search experience for your customers.
Time to Get Exploring…
Have you ever felt limited by the frontend implementation of Klevu’s powerful functionality across your store, or had to wait longer than you would like for a customization?