Please refer to this section of the documentation:
The examples we have provided are NOT to be considered “Production-ready”. Their intention is to help developers learn how to implement the most common requirements in search, in order that you can extract the parts you need and implement in your own theme.
By all means use the examples as a starting point, but please thoroughly test and ensure the functionality suits your needs and amend as required. If there are any bugs or issues in the examples that you have used on a Production store, it would be your responsibility to resolve those issues. We would of course welcome the feedback if you have fixed any bugs so that we could update our examples for other customers.
Yes. This would be a very powerful combination on a Magento store where you already have control over the search results landing page, you would now also have full control over the JS, HTML and CSS of the auto-suggest overlay.
Similar to the answer to why you might move as an existing customer, you should ask yourself how much customisation is expected above and beyond what Klevu JSv1 offers out of the box. If CSS customisation is all that you need, then JSv1 is still a viable option. If you think you might want to move things around, add some custom functionality or change how the search results look then JSv2 should be considered.
Previously with a JSv1 integration you would get a ready-made template to start with which could be customised via the Klevu Merchant Centre or by our development team to remove or amend the elements you don’t need.
With JSv2 you start with a blank slate. You have full control over which elements of search are relevant to your particular integration, and how they should be implemented.
For example, if your design doesn’t include category suggestions in the auto-suggest overlay, in JSv1 this would have required a customisation to remove them, whereas in JSv2 you simply don’t implement that functionality.
Klevu JS Library includes functionality that will detect keystrokes across multiple search boxes and automatically begin Chains of functionality to build an API request, send it, process the response and initialise a templating engine to render the response.
Currently we are focusing our attention on Shopify in order to give greater flexibility to merchants, due to the lack of a Preserve Layout option that is available to our Magento customers.
JSv1 is our existing integration where Klevu hosts the JS, HTML and CSS files which are injected into your website to display the search overlay and search results pages. Any changes to the functionality or look & feel must be handled by Klevu, or managed via the customisation options within the Klevu Merchant Centre.
With JSv2 your own development team must build these JS, HTML and CSS files yourself, and host them within your Ecommerce theme. This gives you direct access to make changes to functionality, look & feel as often and freely as you wish.