@axiapps/axi-design 1.31.0 → 1.33.0

package/README.md

@@ -140,6 +140,8 @@ not "what does the system look like". Everything else is
 | `--axi-textarea-h` | the minimum height of a `<textarea class="axi-input">` | `90px` | `<textarea class="axi-input" style="--axi-textarea-h: 200px">` |
 | `--axi-btn-pad` | the padding inside an `.axi-btn`. The three named steps set it for you; reach for the knob only for a size they do not cover | `12px 20px` | `<button class="axi-btn" style="--axi-btn-pad: 3px 7px">` |
 | `--axi-btn-size` | an `.axi-btn`'s text size, which travels with its padding | `13px` | `<button class="axi-btn" style="--axi-btn-size: 10px">` |
+| `--axi-pill-pad` | the padding inside an `.axi-pill`. The same scale and the same two named steps as the button, because a pill is a button that holds a state | `12px 20px` | `<button class="axi-pill" style="--axi-pill-pad: 3px 7px">` |
+| `--axi-pill-size` | an `.axi-pill`'s text size, which travels with its padding | `13px` | `<button class="axi-pill" style="--axi-pill-size: 10px">` |
 | `--axi-input-pad` | the padding inside an `.axi-input`, for a field that is furniture in a header rather than a control on a page | `11px 12px` | `<input class="axi-input" style="--axi-input-pad: 7px 12px">` |
 | `--axi-input-size` | an `.axi-input`'s text size, which travels with its padding | `14px` | `<input class="axi-input" style="--axi-input-size: 13px">` |
 | `--axi-well-pad` | the padding inside an `.axi-well` | `10px` | `<div class="axi-well" style="--axi-well-pad: 18px">` |

package/dist/axi.css

@@ -448,19 +448,30 @@ button.axi-panel--tile:hover,
    as a generic "selected". Consumers set that colour with --axi-pill-fill,
    on the pill or on any ancestor - it is read through a fallback and never
    declared on the component, which is what keeps both placements working. */
+/* On the button's scale, and deliberately the same numbers. The only thing a
+   pill has that a button does not is a state, so two of them carrying the same
+   13px uppercase label have no reason to be different shapes - and they were:
+   measured at 12px/20px against 10px/9px, the pill's sides less than half the
+   button's, 43px tall against 39px. Side by side that reads as two components
+   rather than one component holding a state. The steps below are the button's
+   steps verbatim for the same reason, and a test holds the two in step. */
 .axi-pill {
   display: inline-flex; align-items: center; gap: 6px;
-  padding: 10px 9px;
+  padding: var(--axi-pill-pad, 12px 20px);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   background: var(--axi-ground);
   color: var(--axi-text-dim);
   font: var(--axi-t-label);
   letter-spacing: var(--axi-ls-label);
+  /* After the `font` shorthand, which sets 13px and would otherwise reset it. */
+  font-size: var(--axi-pill-size, 13px);
   text-transform: uppercase;
   cursor: pointer;
   transition: transform .1s, box-shadow .1s;
 }
+.axi-pill--sm { --axi-pill-pad: 8px 13px; --axi-pill-size: 12px; }
+.axi-pill--xs { --axi-pill-pad: 5px 9px;  --axi-pill-size: 11px; }
 /* :where() for the same reason the button's hover has it - the brighten is
    what a pill that has not been told its colour falls back to, not an override
    of one that has. See rule 6's addendum. */
@@ -661,6 +672,37 @@ button.axi-panel--tile:hover,
   color: var(--axi-accent); font-weight: 900; pointer-events: none;
 }
 
+/* ---------- code ---------- */
+/* A literal the reader is meant to type or recognise character for character:
+   a slash command, a file extension, a URL, a config key. The language already
+   had this style, but only as `.axi-prose code` - reachable by adopting a whole
+   typography layer for a document. A consumer with one command to name inside a
+   sentence of interface copy cannot adopt that layer without restyling the
+   sentence, so it invents a box instead. One real consumer had three spellings
+   for six spans, and the sixth had given up and drawn no box at all.
+
+   So the rule below carries both selectors. Not for brevity - because a code
+   span inside rendered markdown and a code span inside a card are the same
+   object, and the last time this language spelled one object twice the two
+   copies drifted. There is a test that they stay one rule.
+
+   `em`, not `px`: this lands in body copy and in 10px captions alike, and a
+   literal that does not track the text around it reads as a different voice.
+
+   It sits on --axi-ground where .axi-kbd sits on --axi-surface, and the
+   reason is already written down one rule below: a key is raised off what it
+   is printed on, and a quoted literal is sunk into it. */
+.axi-code,
+.axi-prose code {
+  font-family: var(--axi-mono);
+  font-size: .88em;
+  background: var(--axi-ground);
+  color: var(--axi-text);
+  border: var(--axi-border-hairline) solid var(--axi-ink-line);
+  border-radius: var(--axi-radius-sm);
+  padding: 1px 5px;
+}
+
 /* ---------- keyboard key ---------- */
 /* A key on the keyboard, named in the interface: the Esc that closes a
    palette, the Ctrl K that opens it. Drawn as a small control rather than as a
@@ -2595,12 +2637,8 @@ textarea.axi-input {
   border: var(--axi-border-hairline) solid var(--axi-ink-line);
 }
 
-.axi-prose code {
-  font-family: var(--axi-mono); font-size: .88em;
-  background: var(--axi-ground); color: var(--axi-text);
-  border: var(--axi-border-hairline) solid var(--axi-ink-line);
-  border-radius: var(--axi-radius-sm); padding: 1px 5px;
-}
+/* .axi-prose code is declared beside .axi-code in primitives.css: one rule,
+   both selectors, because they are one object. */
 .axi-prose pre {
   margin: 0 0 18px; padding: 14px 16px; overflow-x: auto;
   background: var(--axi-ground);

package/docs/RULES.md

@@ -682,3 +682,23 @@ vacuously while no theme exists, and binds the moment the first file lands.
 4. Add it to the gallery, and check it with the accent switcher — if it does
    not follow the accent, it hard-coded something.
 5. `npm run build` and commit `dist/axi.css` with your source change.
+
+### A style only reachable through a layer will be re-invented
+
+If a style lives at `.some-layer .thing` and nowhere else, then it exists for
+consumers who adopted that layer and for nobody else. Every other consumer that
+needs the same object has to adopt a whole layer to reach one declaration — and
+what it does instead is draw its own. That is not a hypothetical: `.axi-prose
+code` was the language's only word for a quoted literal, and a consumer with six
+literals in its interface copy — none of them in prose — had written three
+different boxes for them, the sixth having given up and drawn none.
+
+So when a layer-scoped style names an object that can appear outside that layer,
+give the object its own class and put **both selectors on one rule**. Not two
+rules that agree: one rule. `.axi-code, .axi-prose code { … }`. Two rules that
+agree today are two rules that disagree after the next edit, and that is how the
+same object ends up with two appearances inside one language — the defect this
+whole section exists to prevent.
+
+The test to write is not "does `.axi-code` exist". It is "are both spellings in
+the same rule", because only the second one fails when someone splits them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiapps/axi-design",
-  "version": "1.31.0",
+  "version": "1.33.0",
   "description": "The design language for the axi suite — flat and outlined, dark, drawn in saturated ink.",
   "type": "module",
   "license": "MIT",

package/src/primitives.css

@@ -174,19 +174,30 @@ button.axi-panel--tile:hover,
    as a generic "selected". Consumers set that colour with --axi-pill-fill,
    on the pill or on any ancestor - it is read through a fallback and never
    declared on the component, which is what keeps both placements working. */
+/* On the button's scale, and deliberately the same numbers. The only thing a
+   pill has that a button does not is a state, so two of them carrying the same
+   13px uppercase label have no reason to be different shapes - and they were:
+   measured at 12px/20px against 10px/9px, the pill's sides less than half the
+   button's, 43px tall against 39px. Side by side that reads as two components
+   rather than one component holding a state. The steps below are the button's
+   steps verbatim for the same reason, and a test holds the two in step. */
 .axi-pill {
   display: inline-flex; align-items: center; gap: 6px;
-  padding: 10px 9px;
+  padding: var(--axi-pill-pad, 12px 20px);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   background: var(--axi-ground);
   color: var(--axi-text-dim);
   font: var(--axi-t-label);
   letter-spacing: var(--axi-ls-label);
+  /* After the `font` shorthand, which sets 13px and would otherwise reset it. */
+  font-size: var(--axi-pill-size, 13px);
   text-transform: uppercase;
   cursor: pointer;
   transition: transform .1s, box-shadow .1s;
 }
+.axi-pill--sm { --axi-pill-pad: 8px 13px; --axi-pill-size: 12px; }
+.axi-pill--xs { --axi-pill-pad: 5px 9px;  --axi-pill-size: 11px; }
 /* :where() for the same reason the button's hover has it - the brighten is
    what a pill that has not been told its colour falls back to, not an override
    of one that has. See rule 6's addendum. */
@@ -387,6 +398,37 @@ button.axi-panel--tile:hover,
   color: var(--axi-accent); font-weight: 900; pointer-events: none;
 }
 
+/* ---------- code ---------- */
+/* A literal the reader is meant to type or recognise character for character:
+   a slash command, a file extension, a URL, a config key. The language already
+   had this style, but only as `.axi-prose code` - reachable by adopting a whole
+   typography layer for a document. A consumer with one command to name inside a
+   sentence of interface copy cannot adopt that layer without restyling the
+   sentence, so it invents a box instead. One real consumer had three spellings
+   for six spans, and the sixth had given up and drawn no box at all.
+
+   So the rule below carries both selectors. Not for brevity - because a code
+   span inside rendered markdown and a code span inside a card are the same
+   object, and the last time this language spelled one object twice the two
+   copies drifted. There is a test that they stay one rule.
+
+   `em`, not `px`: this lands in body copy and in 10px captions alike, and a
+   literal that does not track the text around it reads as a different voice.
+
+   It sits on --axi-ground where .axi-kbd sits on --axi-surface, and the
+   reason is already written down one rule below: a key is raised off what it
+   is printed on, and a quoted literal is sunk into it. */
+.axi-code,
+.axi-prose code {
+  font-family: var(--axi-mono);
+  font-size: .88em;
+  background: var(--axi-ground);
+  color: var(--axi-text);
+  border: var(--axi-border-hairline) solid var(--axi-ink-line);
+  border-radius: var(--axi-radius-sm);
+  padding: 1px 5px;
+}
+
 /* ---------- keyboard key ---------- */
 /* A key on the keyboard, named in the interface: the Esc that closes a
    palette, the Ctrl K that opens it. Drawn as a small control rather than as a

package/src/prose.css

@@ -46,12 +46,8 @@
   border: var(--axi-border-hairline) solid var(--axi-ink-line);
 }
 
-.axi-prose code {
-  font-family: var(--axi-mono); font-size: .88em;
-  background: var(--axi-ground); color: var(--axi-text);
-  border: var(--axi-border-hairline) solid var(--axi-ink-line);
-  border-radius: var(--axi-radius-sm); padding: 1px 5px;
-}
+/* .axi-prose code is declared beside .axi-code in primitives.css: one rule,
+   both selectors, because they are one object. */
 .axi-prose pre {
   margin: 0 0 18px; padding: 14px 16px; overflow-x: auto;
   background: var(--axi-ground);