From c41fb42e16f74173ef4f8082d17244a976e16fb7 Mon Sep 17 00:00:00 2001 From: mikael-lovqvists-claude-agent Date: Wed, 1 Apr 2026 05:06:00 +0000 Subject: [PATCH] Note: split CSS into per-section files with build-step consolidation Co-Authored-By: Claude Sonnet 4.6 --- future-plans.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/future-plans.md b/future-plans.md index 1557e8b..7a7b6cb 100644 --- a/future-plans.md +++ b/future-plans.md @@ -49,6 +49,13 @@ function render() { sync_nav(); SECTION_RENDERERS[section]?.(); } (`views/components.mjs`, `views/grids.mjs`, etc.) that each export their render function and own their local state. +### Split CSS into per-section files +`style.css` is a single large file and getting hard to navigate. Split into +per-section files (`components.css`, `grids.css`, `bins.css`, etc.) plus a +`base.css` for variables, resets, and shared layout. A `make build` step can +concatenate them into a single `style.css` for deployment, keeping the dev +experience clean without adding a bundler dependency. + ### Explicit save in component editor Currently any change in the component detail panel (linking a file, unlinking an inventory entry, etc.) is persisted immediately. This makes it hard to experiment or