Hi all, As part of our GSoC project, we are working on migrating the jenkins.io to vite.js (non-versioned) and Antora (versioned). One of the key improvements we’re exploring is implementing a robust search experience. Currently, jenkins.io <https://www.jenkins.io> uses Algolia for search, and we are considering reusing/migrating the same setup for our Vite.js site.
Before we move forward, we wanted to ask the community for input and guidance: - What is the best way forward to test Algolia for the Vite.js <http://vite.js> site under development? - Is it feasible to extend the existing Algolia setup from jenkins.io to our Vite.js site? - Are there any best practices or pitfalls we should be aware of when integrating Algolia into a new frontend stack? - Would it make sense to consolidate both sites under a shared Algolia index, or should we maintain separate indices? We’d love to hear your thoughts on this approach. If anyone has prior experience with Algolia in the Jenkins ecosystem (or general suggestions for search integration in static sites), your input would be very valuable. Looking forward to your feedback! Best regards, Birajit GSoC contributor Jenkins’25 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAGXhLaqHT2x80_3uGP_DpHeJfXDEVG-UeN98NYAij%3D_Edm3%3D6Q%40mail.gmail.com.
