Hi everyone,
I’d like to open a discussion around the ongoing retooling of Jenkins websites, particularly related to the use of Gatsby and the shift toward Vite.js.
Recently, concerns have been raised across the web development community regarding Gatsby’s long-term support. These include:
- React 19 compatibility issue on GitHub
- Maintenance discussion on GitHub
- “Is Gatsby.js Dead?” – Ikius Blog Post
This topic was first brought up internally by Zbynek Konecny, and after discussions with Kris Stern, Gavin, Damien, and others, we’ve decided to shift the GSoC 2025 project which involves rebuilding the non-versioned documentation content, from Gatsby to Vite.js.
Vite.js offers better build performance, a modern developer experience, and active community support, making it a strong fit for this initiative.
Other Jenkins sites are also under evaluation for potential transitions:
-
Hugo is being considered for some CDF-related sites and possibly for the Contributor Spotlight
-
jenkins.io-components is evolving with dynamic features like modals and tabs: Component demo link
-
Over time, there may be a shift away from Gatsby in the Success Stories and Plugin sites
We are still in the planning phase and open to feedback from the community:
-
Do you maintain a Jenkins website or tool that currently depends on Gatsby?
-
Are there any technical blockers we should keep in mind during this transition?
-
What tools or frameworks would you recommend for static + dynamic content going forward?
We welcome your thoughts and experiences to help guide this transition.
Thanks for reading and looking forward to hearing from you.
Best,
Birajit Saikia
@biru-codeastromer