GSoC 2026 – Update Issue #353 & Guidance

Hi everyone,

I’m Maanvi, a student preparing for GSoC 2026 and excited to contribute to Jenkins. I recently submitted PR #408 to address Issue #353 (Java syntax highlighting for the dark theme). PR link.

After a few initial build failures:

  • I merged the latest main branch changes to resolve build conflicts.

  • Fixed CSS linting errors by converting long hex codes to shorthand according to project style rules.

  • The ‘Jenkins (Required)’ build is now passing! Some infrastructure checks (preview site deployment) are still red, but core validation is :white_check_mark:.

I’d love any feedback on my PR and guidance on how I can contribute more effectively toward GSoC. I’m really eager to learn from the community and make meaningful contributions.

Thanks a lot for your time!

— Maanvi

Hi :waving_hand:

Re the netlify error, related infra helpdesk: [(status|contributors|stats|docs|stories|cn|jenkins-io-components).jenkins.io, Websites PR previews] Netlify billing plan changed: evaluate and act · Issue #4958 · jenkins-infra/helpdesk · GitHub

About your PR, I would suggest adding a section describing how and what you tested for your change.

Hi Hervé! :waving_hand:

Thank you for the clarification regarding the Netlify billing error; that is very helpful to know.

Regarding my PR, I realized after a closer manual inspection that the colors I chose (especially for types and keywords) are still appearing a bit too dark against the Jenkins dark theme.

I am going to submit one more commit now with brighter shorthand hex codes to ensure better contrast. Once that is done and the Jenkins linting check passes, I will add the ‘Testing Performed’ section to the PR description as you suggested.

Any feedback on preferred contrast levels or accessibility considerations would be very welcome!:slightly_smiling_face:

Thanks for your patience and guidance!

Hi Hervé, thanks a lot for the suggestion — that makes sense.:slightly_smiling_face:

Following your feedback, I’ve pushed a new commit to PR #408 where I added a section describing what and how I tested the change.

During visual testing, I noticed that a couple of the previously updated colors still made parts of the documentation hard to read in the dark theme. To address this, I refined those colors and aligned them with the official color palette used on jenkins.io, which provides better contrast and readability.

For testing, I:

  • Compared the previous and updated color schemes side-by-side using Canva for visual comparison.

  • Reviewed readability across code blocks, headings, and inline elements.

  • Confirmed that required CI checks are passing after the update.

I’ve also captured screenshots comparing the old and new formatting to clearly illustrate the improvement.

Please let me know if you’d like me to adjust anything further or test additional scenarios — happy to iterate based on feedback.:blush:

Thanks again for the guidance!

— Maanvi

FTR, Netlify issue on previews should be fixed now cf chore(Jenkinsfile) fix preview deployment in netlify after project name was changed by dduportal · Pull Request #409 · jenkins-infra/docs.jenkins.io · GitHub

Yes @lemeurherve , I have pushed the updated commit and pasted the Form Validation page link (preview).

Quick Update : my first PR addressing syntax highlighting in Jenkins documentation has been accepted.

Thanks for the feedback and support - looking forward to contributing more!

1 Like