@axiapps/axi-design 1.15.0 → 1.17.0

package/README.md

@@ -138,6 +138,9 @@ not "what does the system look like". Everything else is
 | `--axi-check-size` | the size of an `.axi-check` or `.axi-radio` box | `22px` | `<input type="checkbox" class="axi-check" style="--axi-check-size: 16px">` |
 | `--axi-check-fill` | the fill a checked `.axi-check` takes, and the colour of a checked `.axi-radio`'s diamond | `var(--axi-accent)` | `<input type="checkbox" class="axi-check" style="--axi-check-fill: var(--axi-danger)">` |
 | `--axi-textarea-h` | the minimum height of a `<textarea class="axi-input">` | `90px` | `<textarea class="axi-input" style="--axi-textarea-h: 200px">` |
+| `--axi-well-pad` | the padding inside an `.axi-well` | `10px` | `<div class="axi-well" style="--axi-well-pad: 18px">` |
+| `--axi-rail-w` | an `.axi-rail`'s width, for labels longer than the default holds | `208px` | `<aside class="axi-rail" style="--axi-rail-w: 260px">` |
+| `--axi-rail-pad` | the padding inside an `.axi-rail` | `10px` | `<aside class="axi-rail" style="--axi-rail-pad: 6px">` |
 | `--axi-avatar-size` | the size of an `.axi-avatar` square | `40px` | `<span class="axi-avatar" style="--axi-avatar-size: 28px">MS</span>` |
 | `--axi-modal-width` | the maximum width of an `.axi-modal`, before the viewport clamp | `560px` | `<dialog class="axi-modal" style="--axi-modal-width: 760px">` |
 | `--axi-card-strip` | the colour of `.axi-card--strip`'s top strip | `var(--axi-accent)` | `<a class="axi-card axi-card--strip" style="--axi-card-strip: var(--axi-ok)">` |

package/dist/axi.css

@@ -43,6 +43,28 @@
      --axi-ink-on-fill below, on the other side of the same token. */
   --axi-ground-deep: var(--axi-ink-line);
   --axi-rule: #3a4250;            /* internal rules, inside an outlined panel */
+  /* --- the well --- */
+  /* A field sunk INTO a surface rather than raised off one: a table picker's
+     list, a bar's trough, a column of cards standing on the page. The language
+     had no name for it, and every consumer that needed one reached for a second
+     .axi-panel inside the first - two identical fills parted by a line, which
+     reads as one field with a stray rule through it.
+
+     Two tokens because a well is the exact inverse of a panel on both counts.
+     The fill is a SUBTRACTION from whatever is behind it, not a colour of its
+     own: spelled as --axi-ground it is right in this theme, where surfaces are
+     opaque and the page really is what shows through a hole in one, and wrong
+     in a glass theme, where an opaque page colour inside a translucent pane is
+     a black patch rather than a recess. A theme restates it as a darkening at
+     alpha and the panel's own tint carries through.
+
+     The line is --axi-rule and not --axi-ink-line, because ink only reads
+     against a fill lighter than itself. Every outline in this language is
+     near-black on the assumption of a ground the lines can be darker than; a
+     well IS at ground level, so an ink edge round one is a black line on a
+     black field. Raised takes ink, sunk takes the rule. */
+  --axi-well-fill: var(--axi-ground);
+  --axi-well-line: var(--axi-rule);
   --axi-text: #f4f6f9;
   --axi-text-dim: #a7b0be;
   --axi-text-faint: #7c8695;
@@ -251,6 +273,22 @@ a { color: inherit; }
   padding: var(--axi-panel-pad, 26px);
 }
 
+/* ---------- well ---------- */
+/* The panel's inverse: a field sunk into the surface around it rather than
+   raised off it. No block, because a recess casts nothing, and the rule rather
+   than the ink for its edge - see --axi-well-fill in src/tokens.css for why
+   both of those follow from the same fact. Reach for this wherever a second
+   panel inside a panel was the instinct: a picker list beside a table, a column
+   of cards standing on the page, a trough a bar fills. */
+.axi-well {
+  background: var(--axi-well-fill);
+  border: var(--axi-border-control) solid var(--axi-well-line);
+  border-radius: var(--axi-radius);
+  /* Tighter than a panel's 26px: a well is a container for objects that carry
+     their own padding, not a page margin. */
+  padding: var(--axi-well-pad, 10px);
+}
+
 /* ---------- button ---------- */
 .axi-btn {
   display: inline-flex; align-items: center; gap: 8px;
@@ -874,23 +912,167 @@ textarea.axi-input {
   color: var(--axi-text-faint);
   letter-spacing: .09em; text-transform: uppercase;
 }
-.axi-tabs { display: flex; gap: 8px; margin-left: auto; }
-.axi-tabs a {
+/* Anchors and buttons both. A strip that moves between URLs is made of links;
+   a strip inside an application that swaps a view in place is made of buttons,
+   and they look the same because they answer the same question. A button also
+   arrives carrying the UA's own font, fill and cursor, which an anchor does
+   not, so those three are cleared here rather than left to the consumer. */
+.axi-tabs { display: flex; gap: 8px; }
+/* The auto margin belongs to the masthead, not to the strip: it is a statement
+   about where the tabs sit in that row, and a strip standing on its own -
+   spanning a view instead of ending a header - has nothing to push away from. */
+.axi-mast .axi-tabs { margin-left: auto; }
+.axi-tabs a,
+.axi-tabs button {
   padding: 8px 16px;
   font: 800 13.5px/1 var(--axi-sans);
   color: var(--axi-text-dim); text-decoration: none;
+  background: none;
+  cursor: pointer;
   border: var(--axi-border-control) solid transparent;
   border-radius: var(--axi-radius-sm);
 }
-.axi-tabs a:hover { color: var(--axi-text); border-color: var(--axi-rule); }
+.axi-tabs a:hover,
+.axi-tabs button:hover { color: var(--axi-text); border-color: var(--axi-rule); }
 /* The current tab is filled and blocked - the same treatment a pressed pill
    gets, because it is the same idea: this one is on. */
-.axi-tabs a[aria-current="page"] {
+.axi-tabs a[aria-current="page"],
+.axi-tabs button[aria-current="page"] {
+  background: var(--axi-accent);
+  color: var(--axi-accent-ink);
+  border-color: var(--axi-ink-line);
+  box-shadow: var(--axi-shadow-control);
+}
+
+/* A closable tab - a report or a document, an open thing rather than a place.
+   The label and its close control travel together, so the pair is a box and
+   the strip's gap falls between pairs instead of between a tab and its own X.
+
+   The close control is a tab's affordance and not a tab, so it opts out of the
+   tab treatment: no tab padding, no tab weight, and faint until the cursor is
+   on it. Two classes to outrank `.axi-tabs button`, which is one class and one
+   element and would otherwise win on source order alone. */
+/* A document title is arbitrarily long, so the label truncates rather than
+   pushing the close control off the strip. Both boxes need min-width: 0 - a
+   flex item's default min-width is its content, so without it the label simply
+   refuses to shrink and the ellipsis never appears. The consumer sets the width
+   it wants to hold on .axi-tabs__tab. */
+.axi-tabs__tab { display: inline-flex; align-items: center; min-width: 0; }
+.axi-tabs__tab > a:first-child,
+.axi-tabs__tab > button:first-child {
+  min-width: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+.axi-tabs .axi-tabs__close {
+  padding: 0 6px;
+  font: var(--axi-t-micro);
+  color: var(--axi-text-faint);
+  border-color: transparent;
+}
+.axi-tabs .axi-tabs__close:hover { color: var(--axi-text); border-color: transparent; }
+
+/* ---------- rail ---------- */
+/* Vertical navigation, for a set too large for a tab strip to hold. Same
+   grammar as .axi-tabs deliberately - the item you are on is filled with the
+   accent and blocked, the rest are transparent until hovered - because "where
+   am I" is one question and should have one answer however the app happens to
+   be laying it out.
+
+   What a rail adds over a strip is a second level. A category is a place and
+   takes the fill; a section under it is where the page is scrolled to, which is
+   a smaller claim and is drawn as one: brightened text against the dim list
+   around it, no fill, no edge. Two fills at two levels would leave the reader
+   deciding which of them is the answer.
+
+   --axi-rail-w is declared nowhere and read with a fallback, i.e. it is the hook
+   a consumer overrides to widen the rail for longer labels. */
+.axi-rail {
+  display: flex;
+  flex-direction: column;
+  width: var(--axi-rail-w, 208px);
+  flex: none;
+  overflow-y: auto;
+  padding: var(--axi-rail-pad, 10px);
+  background: var(--axi-surface);
+  backdrop-filter: var(--axi-surface-filter);
+  border: var(--axi-border-panel) solid var(--axi-ink-line);
+  border-radius: var(--axi-radius);
+}
+/* A rail that IS the edge of the page rather than a panel standing in the
+   layout - pinned to the viewport, or a drawer's contents. It keeps the one
+   border that faces the content and drops everything that says "this is an
+   object with space around it": no radius on the flush side, and no block,
+   because a block needs somewhere to fall.
+
+   The block is stated as what a free-standing rail has rather than as
+   something the flush one turns off, so there is exactly one box-shadow here
+   and it names the panel block. `box-shadow: none` would be a second spelling
+   of the raise for a theme to miss. */
+.axi-rail:not(.axi-rail--flush) { box-shadow: var(--axi-shadow-panel); }
+.axi-rail--flush {
+  border: 0;
+  border-right: var(--axi-border-panel) solid var(--axi-ink-line);
+  border-radius: 0;
+}
+.axi-rail__nav { display: flex; flex-direction: column; gap: 2px; }
+.axi-rail__item {
+  display: flex;
+  align-items: center;
+  gap: 10px;
+  width: 100%;
+  padding: 8px 10px;
+  font: 800 12.5px/1 var(--axi-sans);
+  color: var(--axi-text-dim);
+  text-align: left;
+  background: transparent;
+  border: var(--axi-border-control) solid transparent;
+  border-radius: var(--axi-radius-sm);
+  cursor: pointer;
+}
+.axi-rail__item:hover { color: var(--axi-text); background: var(--axi-surface-raised); }
+/* The same treatment a pressed pill and a current tab get. Only ever one of
+   these on screen. Any aria-current value, because the right one depends on
+   what the rail navigates - `page` for a view, `location` for a place within
+   one - and the fill means the same thing either way. */
+.axi-rail__item[aria-current],
+.axi-rail__item[aria-current]:hover {
   background: var(--axi-accent);
   color: var(--axi-accent-ink);
   border-color: var(--axi-ink-line);
   box-shadow: var(--axi-shadow-control);
 }
+/* An icon beside a label is a label for it, not a second accent - so it takes
+   the faint tone, and inside a filled item it follows the item's ink. */
+.axi-rail__item .axi-icon { color: var(--axi-text-faint); }
+.axi-rail__item[aria-current] .axi-icon { color: var(--axi-accent-ink); }
+/* The second level, indented under the item it belongs to. */
+.axi-rail__sub { display: flex; flex-direction: column; margin: 3px 0 5px 10px; }
+.axi-rail__subitem {
+  padding: 5px 8px;
+  font: 700 11.5px/1.3 var(--axi-sans);
+  text-align: left;
+  color: var(--axi-text-faint);
+  background: transparent;
+  border: 0;
+  border-radius: var(--axi-radius-sm);
+  cursor: pointer;
+}
+.axi-rail__subitem:hover { color: var(--axi-text-dim); background: var(--axi-surface-raised); }
+.axi-rail__subitem[aria-current] { color: var(--axi-text); }
+/* An annotation on an item, not a measurement of it, so rule 5 draws it
+   outlined rather than filled. */
+.axi-rail__mark {
+  margin-left: auto;
+  padding: 2px 5px;
+  font: var(--axi-t-micro);
+  letter-spacing: .04em;
+  text-transform: uppercase;
+  color: var(--axi-meta);
+  border: var(--axi-border-hairline) solid var(--axi-meta);
+  border-radius: var(--axi-radius-sm);
+}
 
 /* ---------- notice ---------- */
 .axi-notice {
@@ -1205,7 +1387,8 @@ textarea.axi-input {
 
 @media (max-width: 640px) {
   .axi-mast__in { min-height: 0; padding: 10px 16px; gap: 12px; }
-  .axi-tabs { margin-left: 0; width: 100%; overflow-x: auto; }
+  .axi-mast .axi-tabs { margin-left: 0; }
+  .axi-tabs { width: 100%; overflow-x: auto; }
   /* The offset blocks eat horizontal room a phone does not have, so the panel
      step drops to the control step here rather than to an invented number.
      The card's hover has to come down with it - left alone it kept deepening

package/dist/themes/glass.css

@@ -10,6 +10,7 @@
   --axi-ink-line: rgba(180, 200, 255, .16);
   --axi-rule: rgba(180, 200, 255, .14);
   --axi-ground-deep: #0c0e12;
+  --axi-well-fill: rgba(6, 8, 14, .32);
   --axi-accent-ink: #0c0e12;
   --axi-ink-on-fill: #0c0e12;
   --axi-text: #f2f5fb;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiapps/axi-design",
-  "version": "1.15.0",
+  "version": "1.17.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

@@ -29,6 +29,22 @@
   padding: var(--axi-panel-pad, 26px);
 }
 
+/* ---------- well ---------- */
+/* The panel's inverse: a field sunk into the surface around it rather than
+   raised off it. No block, because a recess casts nothing, and the rule rather
+   than the ink for its edge - see --axi-well-fill in src/tokens.css for why
+   both of those follow from the same fact. Reach for this wherever a second
+   panel inside a panel was the instinct: a picker list beside a table, a column
+   of cards standing on the page, a trough a bar fills. */
+.axi-well {
+  background: var(--axi-well-fill);
+  border: var(--axi-border-control) solid var(--axi-well-line);
+  border-radius: var(--axi-radius);
+  /* Tighter than a panel's 26px: a well is a container for objects that carry
+     their own padding, not a page margin. */
+  padding: var(--axi-well-pad, 10px);
+}
+
 /* ---------- button ---------- */
 .axi-btn {
   display: inline-flex; align-items: center; gap: 8px;

package/src/shells.css

@@ -48,23 +48,167 @@
   color: var(--axi-text-faint);
   letter-spacing: .09em; text-transform: uppercase;
 }
-.axi-tabs { display: flex; gap: 8px; margin-left: auto; }
-.axi-tabs a {
+/* Anchors and buttons both. A strip that moves between URLs is made of links;
+   a strip inside an application that swaps a view in place is made of buttons,
+   and they look the same because they answer the same question. A button also
+   arrives carrying the UA's own font, fill and cursor, which an anchor does
+   not, so those three are cleared here rather than left to the consumer. */
+.axi-tabs { display: flex; gap: 8px; }
+/* The auto margin belongs to the masthead, not to the strip: it is a statement
+   about where the tabs sit in that row, and a strip standing on its own -
+   spanning a view instead of ending a header - has nothing to push away from. */
+.axi-mast .axi-tabs { margin-left: auto; }
+.axi-tabs a,
+.axi-tabs button {
   padding: 8px 16px;
   font: 800 13.5px/1 var(--axi-sans);
   color: var(--axi-text-dim); text-decoration: none;
+  background: none;
+  cursor: pointer;
   border: var(--axi-border-control) solid transparent;
   border-radius: var(--axi-radius-sm);
 }
-.axi-tabs a:hover { color: var(--axi-text); border-color: var(--axi-rule); }
+.axi-tabs a:hover,
+.axi-tabs button:hover { color: var(--axi-text); border-color: var(--axi-rule); }
 /* The current tab is filled and blocked - the same treatment a pressed pill
    gets, because it is the same idea: this one is on. */
-.axi-tabs a[aria-current="page"] {
+.axi-tabs a[aria-current="page"],
+.axi-tabs button[aria-current="page"] {
+  background: var(--axi-accent);
+  color: var(--axi-accent-ink);
+  border-color: var(--axi-ink-line);
+  box-shadow: var(--axi-shadow-control);
+}
+
+/* A closable tab - a report or a document, an open thing rather than a place.
+   The label and its close control travel together, so the pair is a box and
+   the strip's gap falls between pairs instead of between a tab and its own X.
+
+   The close control is a tab's affordance and not a tab, so it opts out of the
+   tab treatment: no tab padding, no tab weight, and faint until the cursor is
+   on it. Two classes to outrank `.axi-tabs button`, which is one class and one
+   element and would otherwise win on source order alone. */
+/* A document title is arbitrarily long, so the label truncates rather than
+   pushing the close control off the strip. Both boxes need min-width: 0 - a
+   flex item's default min-width is its content, so without it the label simply
+   refuses to shrink and the ellipsis never appears. The consumer sets the width
+   it wants to hold on .axi-tabs__tab. */
+.axi-tabs__tab { display: inline-flex; align-items: center; min-width: 0; }
+.axi-tabs__tab > a:first-child,
+.axi-tabs__tab > button:first-child {
+  min-width: 0;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+}
+.axi-tabs .axi-tabs__close {
+  padding: 0 6px;
+  font: var(--axi-t-micro);
+  color: var(--axi-text-faint);
+  border-color: transparent;
+}
+.axi-tabs .axi-tabs__close:hover { color: var(--axi-text); border-color: transparent; }
+
+/* ---------- rail ---------- */
+/* Vertical navigation, for a set too large for a tab strip to hold. Same
+   grammar as .axi-tabs deliberately - the item you are on is filled with the
+   accent and blocked, the rest are transparent until hovered - because "where
+   am I" is one question and should have one answer however the app happens to
+   be laying it out.
+
+   What a rail adds over a strip is a second level. A category is a place and
+   takes the fill; a section under it is where the page is scrolled to, which is
+   a smaller claim and is drawn as one: brightened text against the dim list
+   around it, no fill, no edge. Two fills at two levels would leave the reader
+   deciding which of them is the answer.
+
+   --axi-rail-w is declared nowhere and read with a fallback, i.e. it is the hook
+   a consumer overrides to widen the rail for longer labels. */
+.axi-rail {
+  display: flex;
+  flex-direction: column;
+  width: var(--axi-rail-w, 208px);
+  flex: none;
+  overflow-y: auto;
+  padding: var(--axi-rail-pad, 10px);
+  background: var(--axi-surface);
+  backdrop-filter: var(--axi-surface-filter);
+  border: var(--axi-border-panel) solid var(--axi-ink-line);
+  border-radius: var(--axi-radius);
+}
+/* A rail that IS the edge of the page rather than a panel standing in the
+   layout - pinned to the viewport, or a drawer's contents. It keeps the one
+   border that faces the content and drops everything that says "this is an
+   object with space around it": no radius on the flush side, and no block,
+   because a block needs somewhere to fall.
+
+   The block is stated as what a free-standing rail has rather than as
+   something the flush one turns off, so there is exactly one box-shadow here
+   and it names the panel block. `box-shadow: none` would be a second spelling
+   of the raise for a theme to miss. */
+.axi-rail:not(.axi-rail--flush) { box-shadow: var(--axi-shadow-panel); }
+.axi-rail--flush {
+  border: 0;
+  border-right: var(--axi-border-panel) solid var(--axi-ink-line);
+  border-radius: 0;
+}
+.axi-rail__nav { display: flex; flex-direction: column; gap: 2px; }
+.axi-rail__item {
+  display: flex;
+  align-items: center;
+  gap: 10px;
+  width: 100%;
+  padding: 8px 10px;
+  font: 800 12.5px/1 var(--axi-sans);
+  color: var(--axi-text-dim);
+  text-align: left;
+  background: transparent;
+  border: var(--axi-border-control) solid transparent;
+  border-radius: var(--axi-radius-sm);
+  cursor: pointer;
+}
+.axi-rail__item:hover { color: var(--axi-text); background: var(--axi-surface-raised); }
+/* The same treatment a pressed pill and a current tab get. Only ever one of
+   these on screen. Any aria-current value, because the right one depends on
+   what the rail navigates - `page` for a view, `location` for a place within
+   one - and the fill means the same thing either way. */
+.axi-rail__item[aria-current],
+.axi-rail__item[aria-current]:hover {
   background: var(--axi-accent);
   color: var(--axi-accent-ink);
   border-color: var(--axi-ink-line);
   box-shadow: var(--axi-shadow-control);
 }
+/* An icon beside a label is a label for it, not a second accent - so it takes
+   the faint tone, and inside a filled item it follows the item's ink. */
+.axi-rail__item .axi-icon { color: var(--axi-text-faint); }
+.axi-rail__item[aria-current] .axi-icon { color: var(--axi-accent-ink); }
+/* The second level, indented under the item it belongs to. */
+.axi-rail__sub { display: flex; flex-direction: column; margin: 3px 0 5px 10px; }
+.axi-rail__subitem {
+  padding: 5px 8px;
+  font: 700 11.5px/1.3 var(--axi-sans);
+  text-align: left;
+  color: var(--axi-text-faint);
+  background: transparent;
+  border: 0;
+  border-radius: var(--axi-radius-sm);
+  cursor: pointer;
+}
+.axi-rail__subitem:hover { color: var(--axi-text-dim); background: var(--axi-surface-raised); }
+.axi-rail__subitem[aria-current] { color: var(--axi-text); }
+/* An annotation on an item, not a measurement of it, so rule 5 draws it
+   outlined rather than filled. */
+.axi-rail__mark {
+  margin-left: auto;
+  padding: 2px 5px;
+  font: var(--axi-t-micro);
+  letter-spacing: .04em;
+  text-transform: uppercase;
+  color: var(--axi-meta);
+  border: var(--axi-border-hairline) solid var(--axi-meta);
+  border-radius: var(--axi-radius-sm);
+}
 
 /* ---------- notice ---------- */
 .axi-notice {
@@ -379,7 +523,8 @@
 
 @media (max-width: 640px) {
   .axi-mast__in { min-height: 0; padding: 10px 16px; gap: 12px; }
-  .axi-tabs { margin-left: 0; width: 100%; overflow-x: auto; }
+  .axi-mast .axi-tabs { margin-left: 0; }
+  .axi-tabs { width: 100%; overflow-x: auto; }
   /* The offset blocks eat horizontal room a phone does not have, so the panel
      step drops to the control step here rather than to an invented number.
      The card's hover has to come down with it - left alone it kept deepening

package/src/tokens.css

@@ -39,6 +39,28 @@
      --axi-ink-on-fill below, on the other side of the same token. */
   --axi-ground-deep: var(--axi-ink-line);
   --axi-rule: #3a4250;            /* internal rules, inside an outlined panel */
+  /* --- the well --- */
+  /* A field sunk INTO a surface rather than raised off one: a table picker's
+     list, a bar's trough, a column of cards standing on the page. The language
+     had no name for it, and every consumer that needed one reached for a second
+     .axi-panel inside the first - two identical fills parted by a line, which
+     reads as one field with a stray rule through it.
+
+     Two tokens because a well is the exact inverse of a panel on both counts.
+     The fill is a SUBTRACTION from whatever is behind it, not a colour of its
+     own: spelled as --axi-ground it is right in this theme, where surfaces are
+     opaque and the page really is what shows through a hole in one, and wrong
+     in a glass theme, where an opaque page colour inside a translucent pane is
+     a black patch rather than a recess. A theme restates it as a darkening at
+     alpha and the panel's own tint carries through.
+
+     The line is --axi-rule and not --axi-ink-line, because ink only reads
+     against a fill lighter than itself. Every outline in this language is
+     near-black on the assumption of a ground the lines can be darker than; a
+     well IS at ground level, so an ink edge round one is a black line on a
+     black field. Raised takes ink, sunk takes the rule. */
+  --axi-well-fill: var(--axi-ground);
+  --axi-well-line: var(--axi-rule);
   --axi-text: #f4f6f9;
   --axi-text-dim: #a7b0be;
   --axi-text-faint: #7c8695;