Hey Bobylito, and thanks
I don’t think I was aware of the search for facet values option. Is there a demo I can see somewhere before I go testing it out?
Instantsearch.js has been great! Not too much I can say about it really, it just works. From memory, the only thing I really had to mess with is code to handle the page heading as a new search is made. E.g. If you come in via a designer page - http://allthedresses.com.au/designer/Realisation - you’ll see the heading above the results is “Realisation”. I want this to disappear as soon as the designer filter becomes anything other than just “Realisation” on its own.
In order to get the best SEO, I load all content first seen by the user within the original HTML source markup. I do this by emulating what instantsearch does but via the Algolia PHP API. Then, as soon as the page loads, instantsearch takes over and runs the same queries, and populates the page content again. This step is unnecessary as the content has already been loaded with the original page, but I didn’t know of any other way to handle it. It would be awesome if some built-in instantsearch functions could cater for this, whereby you can pass in the starting content for results and filters. It will result in faster page load as well as a reduction in queries to Algolia. I hope this is making sense…
The Algolia infinitescroll code needs a bit of work, which I have given feedback via the discourse topic on SEO and on github.