VS Code Theme Collections

Overview

VS Code Theme Collections is a pair of Visual Studio Code colour theme extensions built on one premise: an editor should feel like somewhere rather than nowhere. Instead of abstract palettes, each theme is anchored to a real place and named for it — basalt and spray at the Victoria Falls gorge, jacaranda haze over Harare, warm Bulawayo sandstone, the Namib desert under moonlight, granite drawn from Great Zimbabwe, the Maasai Mara at dusk. Where a country has national colours those are used as seeds rather than as the finished palette: the boldest hue is assigned to keywords, a secondary to strings, and muted slate tones to comments and line numbers, then every colour is pulled toward the landscape the theme is named for so backgrounds carry sand, granite or dusk instead of flat black and white.

The Zimbabwe Theme Collection ships eleven city palettes — six dark and five light — across Harare, Bulawayo, Chitungwiza, Mutare and Victoria Falls. The African Themes Collection ships fourteen, a matched dark and light variant for each of Rwanda, Kenya, Ghana, South Africa, Zimbabwe, Nigeria and Namibia. Twenty-five themes in total, and none of them contain runtime code: every one is a plain JSON document holding a workbench colour map — between twenty-nine and ninety-five keys covering the activity bar, side bar, tabs, status bar, panels, gutter and cursor — alongside TextMate token rules for comments, keywords, strings, functions and types, so chrome and syntax are tuned as one palette rather than drifting apart. Contrast was worked out by hand against real source files rather than generated from seed colours, because generated accents tend to collapse in practice: comments too loud, strings and types too close together, punctuation invisible.

Both extensions share the same distribution pipeline, and it is fully automated. A push to the manifest or the themes directory on the main branch triggers a GitHub Actions workflow that packages the extension into a VSIX on a clean Node 20 runner, reads the version out of the manifest, cuts a GitHub release tagged from that version with generated notes and the package attached, then publishes to the Visual Studio Marketplace through vsce and to Open VSX through ovsx. The second registry matters in practice: Cursor, VSCodium and Gitpod users resolve extensions from Open VSX, and dual publishing means they get the same build on the same day rather than a stale fork. Each publish step is guarded on its token being present, so a fork without credentials still builds. Both collections are MIT licensed.