This fork tracks cncf/gitjobs and we do not intend to maintain our own copy of the UI. Everything here exists to keep that possible: theming is confined to the one place upstream almost never touches, so git merge upstream/main stays clean.

Measured against the repo's own history (285 commits):

So:

• Colours live in @theme. That block defines --color-primary-50 through --color-primary-950, and every bg-primary-*, text-primary-* and border-primary-* utility across all 57 templates derives from it. Rewriting it re-themes the whole application without touching a single template.
• Logos are swapped in place, keeping the upstream filename. Editing header.html to point at a differently named file would mean conflicting with the churniest file in the repo on every merge, to no benefit.
• The neutral palette is not find-and-replaced. There are 482 hardcoded stone-* classes. Rewriting them would create 482 permanent conflict points. Tailwind v4 allows redefining built-in palettes, so --color-stone-* can be overridden in the same @theme block if the greys ever need to change.

python3 dronecode-theme/theme.py list
python3 dronecode-theme/theme.py verify --all
python3 dronecode-theme/theme.py apply <name>
cargo build -p gitjobs-server      # Tailwind runs from build.rs

apply rewrites only the @theme block. Switching themes is one command and one file in the diff.

apply refuses to write a theme that fails, because the failures are not hypothetical: these pairings are compiled into the component classes and cannot be adjusted without editing templates.

The ramp is also checked for monotonic lightness, since a scale whose steps collapse into one another looks broken in real interface chrome even when every contrast pair passes.

Worth knowing: the upstream CNCF palette fails two of these, with both the primary button and links at 4.11:1. It is kept as cncf-original for comparison and rollback, and it is the reason apply validates rather than trusts.

The Dronecode logo greens are light. Measured against white:

So the vivid brand green cannot be primary-600. It belongs mid-ramp around step 400–500, with the darker steps derived from it. Any theme that puts the literal logo green on a button produces unreadable white text.