Hi @krisstern and the Jenkins GSoC team,
I am Ashutosh Mishra, proficient in Python, Java, JavaScript, and C++ with MERN stack experience. As an active Jenkins contributor, I am passionate about modernizing infrastructure and simplifying developer workflows to ensure long-term project health.
I’ve been actively contributing to the jenkins.io repository recently- including work on roadmap filters and validator fixes which helped me better understand the current architecture and build workflow. While working on those issues, I started analyzing the Contributor Spotlight implementation more closely, especially the Gatsby + GraphQL setup.
From my understanding:
The site is fully static.
→GraphQL is primarily used because of Gatsby’s data layer.
→Contributor data comes from local AsciiDoc files.
→The build outputs static assets integrated into the Jenkins ecosystem.
My proposed direction:
→Migrate from Gatsby to Vite + React (latest stable versions).
→Remove the GraphQL layer.
→Use structured JSON generated from existing AsciiDoc files (or keep AsciiDoc if required).
→Generate contributor pages at build time.
Preserve:
-Current URL structure
-Static output (public/)
-Existing CI/CD workflow
-UI/UX improvements:
-Modernized landing page
-Improved spotlight profile layout
-Better responsiveness
-Accessibility improvements
-Performance optimization
-Proposed phased approach:
-Functional parity in Vite + React
-UI/UX redesign
-Performance & accessibility improvements
-Documentation of migration process
-Before drafting the full proposal, I’d like to confirm:
-Are there strict SEO or permalink constraints?
-Should AsciiDoc remain the canonical data source?
Is incremental migration preferred?
If this aligns with expectations, I’ll prepare a structured 175-hour proposal with milestones and risk planning.
Best,
Ashutosh