Collapsing is only possible for pages, not headings, so I had to
combine platforms and modules into a single section and nest them
under draft pages.
Later, we could migrate some content from the configuration page to
these draft pages to make the flow of the book more natural.
This has two benefits:
1. It will be displayed when browsing the module source code on
GitHub.
2. It prevents the documentation inadvertently disappearing if the
module directory is renamed.
The tinted-theming repository has updated its scheme for themes such
that colors are located under the key `palette` [1] and such that each
color is # prefixed [2]. These changes update the documentation to
reflect this new schema.
[1]
4caed9a8f5
[2]
61058a8d2e
The style of these two were inconsistent with the rest of the
documentation corpus.
Link: https://github.com/danth/stylix/pull/769
Reviewed-by: Daniel Thwaites <danth@danth.me>
Reviewed-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
Resolve the following 'magick convert' deprecation warning:
WARNING: The convert command is deprecated in IMv7, use "magick"
instead of "convert" or "magick convert"
Reviewed-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
Remove legacy documentation about commit message conventions predating
the standardized format introduced in commit bf31640f49 ("doc: specify
commit message format") on 2024-01-23, with the final GitMoji usage in
commit 5a7f3f15cc ("Add guide for creating modules 📝").
Apparently `../modules` is creating a separate derivation that contains
only that folder, so it's now separate from the flake source. But this
transient derivation isn't mentioned explicitly anywhere in the flake
outputs. It makes it impossible to target those modules in
`disabledModules` directive.
For example, after this change is applied, users can solve issues like
https://github.com/danth/stylix/issues/577 locally, by just adding the
following snippet to their configuration:
disabledModules = [ "${inputs.stylix}/modules/regreet/nixos.nix" ];
Reviewed-by: Daniel Thwaites <danthwaites30@btinternet.com>
Reviewed-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
> The 'base16-schemes' package uses the 'tinted-theming/base16-schemes'
> repository, which has now been archived by the owner in favor of
> 'tinted-theming/schemes'
>
> -- https://github.com/NixOS/nixpkgs/issues/285671
Add a 'stylix.enable' option to enable or disable all Stylix modules in
order to resolve issues similar to [2].
To align with the default 'lib.mkEnableOption' [1] behavior,
'stylix.enable' defaults to 'false'.
BREAKING CHANGE: Stylix is disabled by default. To enable it, use:
stylix.enable = true;
[1]: https://github.com/NixOS/nixpkgs/blob/23.11/lib/options.nix#L91-L105
[2]: https://github.com/danth/stylix/issues/216
Co-authored-by: Daniel Thwaites <danthwaites30@btinternet.com>
Co-authored-by: Jalil David Salamé Messina <jalil.salame@gmail.com>
Co-authored-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
The attrset is used heavily in styllix's modules, but the docs don't contain even a top-level explanation of its value. Though you can gather most it from skimming `base16.nix`, I think stylix should provide an entry point for users, interested in using their color schemes outside of stylix. I base this assumption on personal anecdote of people not having a good understanding of exported values even after extended usage and implementing parallel parsing logic for color scheme files.
The function implements a fairly popular feature and is pretty old, but never gets mentioned in the docs. In fact, I only found it by randomly going through the sources. As a result, a person I spoke to wrote the section above describing a re-implementation of the function, which does work but doesn't need to be the default approach.
This change will improve discoverability of the codebase and direct users to a more standardized implementation.
P.S. `base16-schemes` changed `catppuccin.yaml` to a couple of variant themes, which is represented in this commit.
I've noticed quite a few pull requests are being submitted with formats
such as feat(abc): or target: at the start of the message.
It will be helpful to have a specific format for this to keep things
consistent.
The Tinted Theming repository is now packaged in Nixpkgs, so we
don't need to list other ways to obtain it.
Also simplified the links to the preview as `$XDG_CONFIG_HOME`
is rarely modified.
