tinted-theming / base16-schemes Goto Github PK

Right now 0.9 build tools should be able to work with this repo AFAIK. Therefore, should we create a tag/release of this repo for legacy uses? Either matching versions with the spec or perhaps it's own release numbering with the README explaining which version is compatible with which spec version?

IE, I propose:

• Release version 0.9 today as spec 0.9 compatible and note this in the README.

When we start adding new (potentially incompatible) data to the yml files that would break the compatibility with older builders and we can point people back to the 0.9 point, etc.

All these themes have names which, when "normalized" to obtain a slug don't line up with the filename.

blueforest
brushtrees-dark
brushtrees
darkviolet
greenscreen
heetch
icy
irblack
seti
solarflare-light
solarflare
synth-midnight-dark
synth-midnight-light
tube
windows-highcontrast-light
windows-highcontrast

We've got a few options:

1. Rename the files (which will change the output filename)
2. Change the scheme names to match the files
3. Add a slug property allowing scheme authors to override the slug

For context: sainnhe/everforest#40 (comment)

This theme was imported from a (possibly?) old upstream PR, but it has since undergone subtle changes so the color palette is slightly outdated.

I'm creating this issue as a TODO for myself and will address it within the next 3 days (unless somebody else steps in before I do).

Catppuccin (home https://github.com/catppuccin/base16) added in #24 is not listed in the readme.

I would open a PR to add it but I'm not clear if the variants should be listed in the readme or not. What's the policy/ expectation?

It currently takes a lot of scrolling to get to the README of the repo. Placing schemes in one folder (except the root) will improve organization. Plus, it can leave room for more configuration files for Makefiles, CI, and other purposes.

Once agreed on I can make a pull request.