NAHO

The style guide could demonstrate the most common use cases with color aliases: https://github.com/danth/stylix/issues/207.

> The solution I'm considering mimics vim's highlight groups VIM's highlight groups might be the most scalable and practical solution I know of. It would resolve nearly all our open...

We should consider specifying [border widths](https://github.com/danth/stylix/pull/410#discussion_r1632058909) and [font usage](https://github.com/danth/stylix/pull/493#discussion_r1702027663).

> I have since read more about fonts in plymouth and as i understand it only truetype and opentype are supported with opentype being the preferred format. I am not...

> This may be more convenient to fill out if we use [issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), since there would be no need to delete the comments under each section. Mandatory sections can...

Superseded-by: https://github.com/danth/stylix/pull/516

> # Todos for this PR > > * documentation (lucky last) Assuming we implement potentially all of VIM's highlight groups > our documentation could simply link to VIM's highlight...

> Currently we've got a flat dir so: `./swatches/button-active-hovered.nix` would change into either: > > 1. `./swatches/button/active/hovered.nix` > > or > > 2. `./swatches/button/active/hovered/default.nix` I believe `./swatches/button/active/hovered/default.nix` to be more...

Related: - https://github.com/danth/stylix/issues/249

> > ``` > > treewide: integrate linters and formatters into nix develop > > ``` > > What is the reasoning for this to be integrated into nix develop...