docs(roadmap): close the sanitize file-audit; menu grouping is ongoing
The repo-organization re-check found nothing to move: no orphaned modules
(keybinds.nix is a data import, not a HM module), no dead-code markers or
editor/backup cruft, every themes/<slug>.json pairs with its optional
overrides dir, and hosts/{default,live} are the reference + ISO hosts.
Recorded the one open decision: no formatter is declared and the .nix
hand-formatting is deliberate, so adopting nixfmt is a maintainer call,
left untouched. Also marked the menu category grouping a standing
convention — new menu-facing features get placed in the right submenu.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -47,6 +47,10 @@ how to override it. Items marked ✓ are shipped.
|
|||||||
straight (bypassing the menu), and the self-gated entries still hide when
|
straight (bypassing the menu), and the self-gated entries still hide when
|
||||||
unavailable. Remaining (optional): a **Look & Feel** category once there are
|
unavailable. Remaining (optional): a **Look & Feel** category once there are
|
||||||
more appearance toggles to group with Theme (night-light, wallpaper).
|
more appearance toggles to group with Theme (night-light, wallpaper).
|
||||||
|
**General pattern (ongoing):** the grouping is a standing convention, not a
|
||||||
|
one-off — any new feature that earns a menu entry must be placed in the
|
||||||
|
right submenu (don't let the root creep back to a flat list), with its
|
||||||
|
direct `SUPER+CTRL+<mnemonic>` bind and self-gating as applicable.
|
||||||
- ✓ **Menu modules from rofi plugins:** the old `calc` flow committed the
|
- ✓ **Menu modules from rofi plugins:** the old `calc` flow committed the
|
||||||
expression blind (result only in the *next* menu's `-mesg`) and `qalc -t`
|
expression blind (result only in the *next* menu's `-mesg`) and `qalc -t`
|
||||||
misparsed common phrasings (`15% of 200` → `rem(15, 1 B)`, the natural-
|
misparsed common phrasings (`15% of 200` → `rem(15, 1 B)`, the natural-
|
||||||
@@ -173,8 +177,18 @@ how to override it. Items marked ✓ are shipped.
|
|||||||
a batch is tested — rolling, no tags. Brought `main` current (it was a
|
a batch is tested — rolling, no tags. Brought `main` current (it was a
|
||||||
stale legacy-merge), and deleted the dead `refactor` / `wave/nixos-26.05`
|
stale legacy-merge), and deleted the dead `refactor` / `wave/nixos-26.05`
|
||||||
branches (kept `legacy` for history). See the comment in `flake.nix`.
|
branches (kept `legacy` for history). See the comment in `flake.nix`.
|
||||||
- Remaining (optional): re-check that every file still earns its place
|
- ✓ re-checked that every file earns its place under the
|
||||||
under the `modules`/`hosts`/`themes`/`pkgs`/`tools` rule of thumb.
|
`modules`/`hosts`/`themes`/`pkgs`/`tools` rule of thumb: no orphaned
|
||||||
|
modules (`keybinds.nix` is a *data* module `import`-ed by hyprland/rofi,
|
||||||
|
so correctly absent from `default.nix`), no dead-code markers, no
|
||||||
|
editor/backup cruft, each `themes/<slug>.json` palette pairs with its
|
||||||
|
optional `<slug>/` overrides dir, and `hosts/{default,live}` are the
|
||||||
|
documented reference + ISO hosts. Structure is clean as-is.
|
||||||
|
- Open decision (deferred): the repo declares **no formatter** (no flake
|
||||||
|
`formatter`, no `.editorconfig`); `.nix` files use deliberate aligned
|
||||||
|
hand-formatting, so `nixfmt-rfc-style --check` flags ~33 files. Adopting a
|
||||||
|
formatter would be a one-time repo-wide reformat that flattens that
|
||||||
|
alignment — a maintainer call, not a silent cleanup, so left untouched.
|
||||||
- **Full docs review & restructure:** a dedicated pass over all the prose,
|
- **Full docs review & restructure:** a dedicated pass over all the prose,
|
||||||
not just the code-adjacent cleanup the repo-sanitize item covers. The
|
not just the code-adjacent cleanup the repo-sanitize item covers. The
|
||||||
README has grown to ~540 lines with a ~200-line roadmap inline — the
|
README has grown to ~540 lines with a ~200-line roadmap inline — the
|
||||||
|
|||||||
Reference in New Issue
Block a user