@nadicodeai/design-system 12.1.15 → 12.1.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/DESIGN.md +2 -0
- package/package.json +1 -1
package/DESIGN.md
CHANGED
|
@@ -389,6 +389,8 @@ A product page is one of five compositions, each answering one question first:
|
|
|
389
389
|
| Configuration | What can I change? | A centred reading column of titled sections, help beside each field, a local save and recovery. |
|
|
390
390
|
| Library | What reusable thing can I use? | Kind, text identity, description, source and revision; detail shows content and requirements. |
|
|
391
391
|
|
|
392
|
+
Every setting is that Configuration composition, whether it belongs to the person, to the platform or to one record's Settings tab, so the column keeps its width and its field layout from one entry of a settings menu to the next, and each section saves its own fields from its own footer. A table that reaches a reading column keeps the identity and the action beside it and lets its remaining columns fall to the row's supporting detail, rather than widening the page or scrolling sideways.
|
|
393
|
+
|
|
392
394
|
A section earns a card when it owns a decision, not for every label and value. A row links to its object; overflow menus hold occasional commands, and a frequent next action stays visible. A summary on an overview opens the same owner as its tab. Supporting detail collapses only behind a summary that keeps a count, state or consequence.
|
|
393
395
|
|
|
394
396
|
## Elevation & Depth
|