silverwind

Please don't edit `github-dark.user.css` but the files in `src`. In this case, `src/main.css`. Then run `make build` to rebuild.

Got a example?

I've automated the octotree styles, it should generally cover it more completely now in terms of styling. I realize this might make your work of customizing it harder, but at...

I wouldn't do that. `pl-s` is blue in GH's sheet, while `pl-s1` is uncolored (renders as `#333`). Maybe we should just make `pl-s1` the same color as the theme's body...

Adding another syntax system (the 4th one now) will be a lot of work unless we find a way to abstract them further (and possibly generate all the themes from...

`prefers-color-scheme` is not supported in Edge and Opera or older versions of Chrome and Firefox, so I assume wrapping it like that would break it in those browsers (as the...

Support in Stylus seems like the best option so we don't have to require every style to support this. Could a see a dropdown with three options: - Always apply...

`var()` would be nice, but we first need a solid naming scheme for the variables which is rather hard when you have like 30 shades of grey to name. Any...

Regarding syntax rework, I think we should include a "base" dark syntax theme in the style and other syntaxes would be separate "addon" usercss files. That way we can get...

GitHub is already at something like 500+ css vars. I'd say they are overkilling it with making too specific vars and not sharing enough of them. I have written CSS-var...