Studying the contributor-spotlight codebase

Contributing GSoC
1

Hi @krisstern @berviantoleo @iamrajiv,

I am Raj Tayde, applying for GSoC 2026 for the
“Retool Jenkins.io Contributor Spotlight Website” project.

I have been studying the contributor-spotlight codebase
at GitHub - jenkins-infra/contributor-spotlight: Jenkins Contributor Spotlight feature · GitHub and
have identified several areas that align with the
project goals:

Current Technical Observations:

  1. The site uses Gatsby.js with GraphQL for data
    fetching, which adds unnecessary complexity for
    simple contributor data rendering
  2. AsciiDoc files are used for contributor data —
    migrating to JSON/Markdown would simplify the
    data layer significantly
  3. Several open issues (#564, #535, #515) point to
    the same underlying need for modernization
  4. Build times are slow due to Gatsby-specific
    plugin dependencies

My Proposed Approach:

  • Migrate from Gatsby.js to Vite.js + React.js
  • Replace GraphQL layer with static JSON data fetching
  • Improve accessibility (WCAG 2.1 AA compliance)
  • Achieve Lighthouse performance score of 90+
  • Maintain all existing contributor data and URLs

My Jenkins Contribution:
PR #482 merged in echarts-api-plugin
Fixed JENKINS-58404 — build number cropping in diagrams

I would love to discuss:

  1. Is there a preferred approach for data migration
    from AsciiDoc to JSON?
  2. Should contributor URLs remain the same after migration?
  3. Any specific design guidelines to follow?

I will share my full proposal draft soon.
Thank you for your time!

GitHub: Raj-spy