nixos-config/modules/nixos/workflows
Gabriel Arazas a4177f9382
flake-parts/setups: set separate namespace for custom library
This at least allows us to make custom environment-specific library sets.
2024-02-11 15:16:25 +08:00
..
a-happy-gnome nixos/workflows/a-happy-gnome: remove resolved service 2024-02-06 20:18:48 +08:00
knome modules: remove unnecessary function attributes 2023-12-20 10:48:32 +08:00
default.nix flake-parts/setups: set separate namespace for custom library 2024-02-11 15:16:25 +08:00
README.adoc docs: update 2022-11-13 14:03:49 +08:00

These are where my workflows are defined and configured. Basically, workflows are mainly graphical sessions concerned with aesthetics and impose a structured way of using things, this may include Unix rices and good 'ol reliable desktop configurations like my GNOME config. This is where modules will define how youre going to interact with the computer whether you should use something ranging from a full-fledged desktop environment with bells and whistles to a minimalist desktop environment only composing of a window manager, a terminal, and a bar.

The following list is the summary which can also serve as a guideline to developing a workflow module.

  • Due to the bigger scope and importance of this module, there is a limit where you can only enable one theme at a time. You can disable this with config.workflows.disableLimit set to true.

  • Custom themes should be defined in config.workflows.workflows attribute (e.g., options.workflows.workflows.a-happy-gnome, options.workflows.workflows.simple-way). This makes up for a namespace entirely dedicated for setting themes.

  • Using profiles are heavily discouraged and it is better assumed to design and create workflows as if profiles are not imported. This is because profiles are not exported in the flake output. If its something you have to use (e.g., setting up i18n configuration), you have to conditionally set a profile as seen from ../profiles/README.adoc.