We encourage Jenkins users to create themes and to share them.
Such themes could be a great way to experiment with UI enhancements,
and we would be happy to consider enhancements from them for a default Jenkins theme.
To improve the user experience,
please consider the following recommendations:
-
Explicitly document compatibility for themes.
-
Compatibility documentation should include: required theme plugins and versions,
target Jenkins core version,
plugin requirements and versions if applicable (UI/CSS are overridden), and
browser compatibility.
-
Examples of such documentation: Jenkins Atlassian Theme, Neo2
-
Version themes with tags on Git and to maintain changelogs with explicit references to changes in the supported versions (e.g. see our release drafter documentation as one of the ways to automate changelogs).
-
Explicitly define an OSI-approved open source license so that users can freely modify and redistribute them.
If you would like to share a story about Jenkins themes,
please let the Advocacy&Outreach SIG know!