@nadicodeai/design-system 12.1.128 → 12.1.130
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 +7 -7
- package/package.json +1 -1
package/DESIGN.md
CHANGED
|
@@ -576,8 +576,8 @@ Text on a colour ground is the pole that clears AA on that hue: `{colors.identit
|
|
|
576
576
|
|
|
577
577
|
- **Feedback** pairs a hue with a soft ground and a deep text step: success (verde), warning (giallo `{colors.warning}`), error (rosso `{colors.error}`), info (cobalto `{colors.info}`). The `-soft` value is the tinted ground of a tag or banner and the `-deep` value is the AA text on it; a component reaches the pair through the `destructive-soft`, `warning-soft`, `success-soft` and `info-soft` roles and their foregrounds. On a solid fill, error takes white text and warning and success take ink in light; in dark all three take `{colors.dark-on-primary}`.
|
|
578
578
|
- **Link** (`{colors.link}`, `{colors.link-deep}`, `{colors.link-bg-soft}`): blue inline links. Success uses its own green roles; link colour never doubles as a health signal.
|
|
579
|
-
- **Workflow states** (`{colors.state-ready}`, `{colors.state-running}`, `{colors.state-review}`, `{colors.state-blocked}`, `{colors.state-complete}`) colour non-text marks only: meter fills and trend icons. Cobalto means in motion and verde means done. A state's word
|
|
580
|
-
- **Status** is always a `StatusBadge` tone with
|
|
579
|
+
- **Workflow states** (`{colors.state-ready}`, `{colors.state-running}`, `{colors.state-review}`, `{colors.state-blocked}`, `{colors.state-complete}`) colour non-text marks only: meter fills and trend icons. Cobalto means in motion and verde means done. A state's word is `StatusBadge`'s, in the foreground colour; never put a raw meter-fill token on text.
|
|
580
|
+
- **Status** is always a `StatusBadge` tone with its shape and a word ("Components").
|
|
581
581
|
|
|
582
582
|
### Category colour
|
|
583
583
|
|
|
@@ -972,7 +972,7 @@ Every example and consuming surface covers its reachable populated, empty, loadi
|
|
|
972
972
|
| [Snippet](https://vercel.com/geist/snippet) | `Snippet` |
|
|
973
973
|
| [Spinner](https://vercel.com/geist/spinner) | `Button`'s `loading` and `WaitingLine`, no Spinner export |
|
|
974
974
|
| [Split Button](https://vercel.com/geist/split-button) | Not built until a page needs it |
|
|
975
|
-
| [Status Dot](https://vercel.com/geist/status-dot) | `StatusBadge
|
|
975
|
+
| [Status Dot](https://vercel.com/geist/status-dot) | `StatusBadge`, whose tone is a shape of dots, never a single dot |
|
|
976
976
|
| [Switch](https://vercel.com/geist/switch) | `SegmentedControl` for two or three exclusive views of one surface; `Tabs` for panels; `ToggleGroup` for pressed buttons; `ThemeModeSwitcher` for the theme |
|
|
977
977
|
| [Table](https://vercel.com/geist/table) | `Table`; `DataTable` for records; `RecordList` for rows that name themselves; `TableCard` and `TableValue` |
|
|
978
978
|
| [Tabs](https://vercel.com/geist/tabs) | `Tabs`, and `TabsNav` with `TabsLink` for URL views |
|
|
@@ -1087,13 +1087,13 @@ An unknown or not-applicable value in a table, a comparison list or a set of fac
|
|
|
1087
1087
|
|
|
1088
1088
|
### Status
|
|
1089
1089
|
|
|
1090
|
-
A status is one `StatusBadge`: a
|
|
1090
|
+
A status is one `StatusBadge`: a shape and a word in one of five tones, with no pill around them, as Vercel sets a deployment's state beside its time. Each tone has its own shape, filled with dots on a honeycomb grid, the material of the Agent orbs: green a circle, blue a diamond, amber a triangle, red a square, and gray an empty ring, because gray is every state with nothing to act on, Ready and Archived as much as Paused. The shape says the tone, so a status reads without colour, and the word says the exact state; a new state picks a tone, never a new shape. Ruled by the owner: the stock tinted pill read as generic, and the status takes the Agents' own dots. `StatusBadge`'s usage page holds the tones; `ProgressChecklist`'s holds how far a record is through the steps that make it ready.
|
|
1091
1091
|
|
|
1092
|
-
The Portal, Nadia and Alveare draw every status with the one `StatusBadge` in `@nadicodeai/ui`, which owns the tones and their
|
|
1092
|
+
The Portal, Nadia and Alveare draw every status with the one `StatusBadge` in `@nadicodeai/ui`, which owns the tones and their shapes; each app keeps only its value-to-tone map in one module, and nothing else chooses a status colour. A status never moves. A single coloured dot is never a status, including beside a visible label and inside an Agent row or filter; the shared package exports no status-dot component. An Agent's orb remains her identity and activity indicator.
|
|
1093
1093
|
|
|
1094
1094
|
In a list or a feed a status shows only for the exception: the record or the event that differs from the others, such as a failure, a revocation or a wait for a person's decision. The usual state shows nothing, so a status never stands on every row. An object's own status sits beside its name in the path ("Product shells").
|
|
1095
1095
|
|
|
1096
|
-
An Agent fleet's operational-state column and a run history's outcome are facts being compared, so each entry keeps its named `StatusBadge`, including Ready and Completed. This exception never permits a
|
|
1096
|
+
An Agent fleet's operational-state column and a run history's outcome are facts being compared, so each entry keeps its named `StatusBadge`, including Ready and Completed. This exception never permits a single coloured dot.
|
|
1097
1097
|
|
|
1098
1098
|
### Activity
|
|
1099
1099
|
|
|
@@ -1226,7 +1226,7 @@ The clear space is one stroke width of the rendered logo on every side. The mini
|
|
|
1226
1226
|
- Do show authentic captures or real-component scenes as "Product views on the website" specifies, with provenance recorded in the repository. Don't use device frames or invented interfaces.
|
|
1227
1227
|
- Do give each thing the corner its role takes on the scale ("Shapes"). Don't choose a corner at the call site: a raised card, like any medium or large surface, takes the larger corner with its material.
|
|
1228
1228
|
- Do give every line one owner, and draw focus only with the focus outline.
|
|
1229
|
-
- Do say a status with a `StatusBadge` tone,
|
|
1229
|
+
- Do say a status with a `StatusBadge` tone, its shape and a word. Don't use colour alone or a bare dot.
|
|
1230
1230
|
- Do open a failure page with one whole cut-out whose idea says what happened, labelled like a work in a museum, above the words on one centre line, with the recovery action leading and the diagnostic code only for a request that stopped. Don't apologise, don't crop the picture, don't joke about lost work, and don't put an orb on a failure page.
|
|
1231
1231
|
- Do use the dotted field only on a canvas where things are arranged. Don't put it behind lists, dashboards, settings or website sections.
|
|
1232
1232
|
- Do build a page from its composition. Don't assemble a page's header, toolbar, rows or menus by hand.
|