@nadicodeai/design-system 12.1.26 → 12.1.27
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 +12 -0
- package/package.json +1 -1
package/DESIGN.md
CHANGED
|
@@ -502,6 +502,17 @@ Who does the work decides how it looks. An Agent's work is that Agent's orb in i
|
|
|
502
502
|
|
|
503
503
|
One wait gets one indicator. A request waiting for a person is not a wait: queued, paused, blocked, failed and done take the status or feedback treatment. A wait is ink; info blue never marks one. Under reduced motion the waiting line breathes in opacity instead of travelling.
|
|
504
504
|
|
|
505
|
+
### Failure surfaces
|
|
506
|
+
|
|
507
|
+
A page that cannot show what was asked for is a picture with the words standing in it. The picture is art direction's, built around the gap, and it fills the plane behind the page in a product and stands beside the words on the website; in the gap sit a mono eyebrow naming the situation, the page's one heading, one plain sentence, and the recovery action, which leads. The words keep their contrast over the picture at every width, and the picture yields to them when the viewport is too small to hold both.
|
|
508
|
+
|
|
509
|
+
Two registers share that composition:
|
|
510
|
+
|
|
511
|
+
- **An absence** is an address or a record that is not there. In its gap, beside the words, stands a short note signed by Nadia. The note is authored copy, not a report of anything an Agent did; it is never the instruction, which is the plain sentence and the action. Where the picture leaves a place for it, Nadia's orb turns there in ambient motion and claims no activity ("Agent orbs"); where the picture does not, the note stands alone. Nothing went wrong, so nothing takes a feedback role and no glyph stands in for the failure. Without a picture the note takes the dashed absence boundary at page scale ("Absence follows its container").
|
|
512
|
+
- **A fault** is a request the product stopped. Its picture is calm and never a joke about lost work, and it carries no note and no Agent, because a stopped request is not a moment for one to perform in. Beside the words stands the evidence: the diagnostic code, the label that names it and one line saying what to do with it. The error pair marks the eyebrow.
|
|
513
|
+
|
|
514
|
+
A failure inside a product's own chrome takes no picture: the picture is the plane the chrome stands on, never something inside it, so an in-chrome failure keeps the words, the note where there is one, and the dashed absence boundary. Identity hue reaches a product failure surface only through the picture and the orb. The words never apologize and never name the mechanism ("Product messages" in `product-design`). On the website a failure surface is an ordinary full-bleed section and takes a section ground like any other.
|
|
515
|
+
|
|
505
516
|
### Agent orbs
|
|
506
517
|
|
|
507
518
|
An Agent is its orb, in every product; there is no other Agent picture. An orb is one of seven forms, `ribbon`, `lattice`, `orbit`, `globe`, `network`, `braid` and `morph`, in one colour a person chose: cobalto, verde or arancio, or none, which draws it in the text colour. Giallo is not offered because it fails 3:1 on white; rosso is not offered because it is the error red. Nadia alone is her striped ribbon, the form `nadia`, azzurro, verde, the text colour and rosso along its whole length, the same at every size and in every state.
|
|
@@ -582,6 +593,7 @@ The clear space is one stroke width of the rendered logo on every side. The mini
|
|
|
582
593
|
- Do round every surface and control at `{rounded.md}`. Don't give a higher surface a bigger corner.
|
|
583
594
|
- Do give every line one owner, and draw focus only with the focus outline.
|
|
584
595
|
- Do say a status with a Badge tone, a mark and a word. Don't use colour alone or a bare dot.
|
|
596
|
+
- Do build a failure page around its picture's gap, with the recovery action leading in it: Nadia's note for a thing that is not there, the diagnostic code for a request that stopped. Don't apologise, and don't put a note or an Agent on a fault.
|
|
585
597
|
- Do use the dotted field only on a canvas where things are arranged. Don't put it behind lists, dashboards, settings or website sections.
|
|
586
598
|
- Do add a rule here before a product needs it. Don't restate a rule in another document; link to it.
|
|
587
599
|
|