dracula-theme

EDIT: other answers point to base16 as a way to do this automatically. Use that. Leaving my previous comment here just in case. I think what the creator is doing is outsourcing the maintenance of each individual app to a maintainer that cares; the themes folder contains pointers to other repos: https://github.com/dracula/dracula-theme/tree/master/themes I think that is a good idea. This could be used to "reverse-engineer a generic platform" relatively easily: 1: Fork Dracula and its themes 3: For each color in Dracula.Palette 4: Find and replace color.hex by color.refjex on themes 5: Find and replace "color.r,color.g,color.b" by color.refrgb on themes 6: Find and replace "color.h,color.s,color.l" by color.refhsl on themes The whole idea would be replacing #282a36 for a reference like `{{Background}}` and then us

Has anyone done a cross-app configuration tool for color themes yet ? It seems most themes just reimplement everything. For example, I like tokyonight, but it seems everyone needs to port it to their favorite tool, just like solarized did: https://github.com/enkia/tokyo-night-vscode-theme#other-port... Even the open source and professional theme Dracula seem to rely on manual porting: https://github.com/dracula/dracula-theme

This is honestly the first time I'm hearing about someone monetizing a color scheme. I didn't even now such a thing was possible. Was it already popular before you started to monetize it? I see that the Github repo [0] has 12k+ stars, so I assume it was already pretty popular beforehand. Did you get more exposure (and GH stars) after the choice to monetize it? Also, what things does the bonus screencast cover? I just downloaded the Alacritty theme [1] and to my liking the background is too bright (I guess I prefer it darker than Dracula hehe), so I changed it to 0x000000, but other than that I like it, it's definitely pleasant on the eyes. [0]: https://github.com/dracula/dracula-theme [1]: https://github.com/dracula/alacritty/tree/af38d360e9589a75a2...