I do not know how many of you actually know Agolia search and how many of took the time to check what you can doing with it.
No offense but by reading your comments I get the impression no one of you actually had a deeper look.
Yes, it is true currently we are using the maybe annoying and not so cool, js snippet.
But this is only the most basic and less time and work/effort included setup.
Actually you can build (and we have planned that already for a long time, but yeah time and ppl factor , you know) super awesome ‘static as in non js’ pages where you ‘easily’ can give the results yout look and feel and also chan choose to show breadcrumbs or what ever you like.
The API of Agolia overs you a lot …
Also like always and I am sorry to bring this up, it is not meant to be personal.
Before we switched to Agolia lots of people where complaining about the results, index and look and feel of the build in sphinx search.
Guess there is no solution to make everyone happy …
If you look under the hood how Agolia indexes and how Sphinx it does, you will be able to discover that if you have good content you get way better and fine grained results with Agolia.
One other point, we never ‘just’ switched because we (or I) made the decision because of what I like more.
We asked various times on various conferences and sprints people for their opinion and also for help.
The first plan was to use Solr or ES, lots of peeps wanted to have that and “it was easy to setup,maintain, etc” but no one had time for it or wanted to help
So yeah I am sorry but talking is one thing and doing the work is something else …
Talk is always cheep …
Take also please in mind that the ‘core docs team’ are basically two people (with sometimes the super awesome help of extreme super awesome community members !!!).