Note: split CSS into per-section files with build-step consolidation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -49,6 +49,13 @@ function render() { sync_nav(); SECTION_RENDERERS[section]?.(); }
|
|||||||
(`views/components.mjs`, `views/grids.mjs`, etc.) that each export their render
|
(`views/components.mjs`, `views/grids.mjs`, etc.) that each export their render
|
||||||
function and own their local state.
|
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
|
### Explicit save in component editor
|
||||||
Currently any change in the component detail panel (linking a file, unlinking an
|
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
|
inventory entry, etc.) is persisted immediately. This makes it hard to experiment or
|
||||||
|
|||||||
Reference in New Issue
Block a user