Hello everyone, I’m Jayraje Shinde, a Second year Computer Science student at AISSMS College of Engineering, Pune, India ,and I’m considering applying for the GSoC 2026 project: Retooling the Jenkins Contributor Spotlight. Before drafting a formal proposal, I wanted to create something solid to better grasp the problem space. I’ve created a functional proof of concept that uses Vite + React in place of the current Gatsby pipeline, which aligns with the project’s direction.
What the POC currently does:
- Parses contributor .adoc files at build time using import.meta.glob (eager) and Asciidoctor.js
- Normalises contributor data and renders individual contributor pages dynamically via React Router
- Adds fuzzy search (Fuse.js) on the landing page across name, location, and slug fields
- Sanitises rendered AsciiDoc HTML with DOMPurify before injection
Live demo: https://jenkins-spotlight-retool-poc-p5v8.vercel.app/
Source: GitHub - Jayraje-Shinde/jenkins-spotlight-retool-poc
A few specific questions worth asking:
- The existing .adoc files use attributes like page-name, page-location, and page-intro — are those enough or should I add more attributed for searching?
- Is client-side fuzzy search the right approach, or would the project prefer a static search index at build time (e.g. pagefind)?
Open for Constructive criticism and also happy to hear feedback on what I’m up to