@getvitops/core 8.3.0-alpha.1 → 8.3.0-alpha.3

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # @getvitops/core
 
+## 8.3.0-alpha.3
+
+## 8.3.0-alpha.2
+
+### Minor Changes
+
+- 0a47856: Build correctness and gaps from the second upstream round.
+
+  - **`@getvitops/emdash`: fixes a circular import that emptied the plugin block map in the static build.** `Section.astro` and `WidgetArea.astro` imported `emdash/ui` statically, which imports `virtual:emdash/block-components`, which is `@getvitops/emdash/astro` again. Depending on import order, every `vitops_*` block inside a section body was dropped from prerendered pages with only a `PortableText [components.type] is missing …` warning. Both now import it lazily, and a test fails if any renderer imports `emdash/ui` statically. No code change needed in sites.
+  - **`@getvitops/cli`: `vitops emdash build`** runs `astro build` and then `check-prerender`, and fails when the build reports a block type with no component (reported once per type). The template's `build`, `deploy` and `deploy:dev` scripts use it; existing sites replace `astro build && vitops emdash check-prerender` with `vitops emdash build`. `check-prerender` also warns (fails with `--strict`) on a page without exactly one `<h1>`.
+  - **`@getvitops/emdash`: `vitops_hero` and `vitops_section` heading level** accepts `h1`–`h6` and `p` (a heading that is styled but not in the outline). The hero defaults to `h1`; set the level to `2` on a page whose layout already renders an `h1` (the template's seed does).
+  - **`@getvitops/emdash`: `vitops_logos`** shows an entry's name as text (`.logos__name`) when it has no image. `@getvitops/core` adds the rule (all formats).
+  - **`@getvitops/emdash`: an empty content widget** (no text, no blocks) no longer renders its title, and an area whose widgets are all empty renders nothing.
+  - **`@getvitops/create`:** the template's `pages` collection gets `urlPattern: "/{slug}"` (the sitemap listed `/pages/<slug>`, which 404s; existing sites change it under Content Types), and `.gitignore` ignores only `src/styles/tailwind.css` and `tokens.json`, so site CSS kept in `src/styles/` is committed.
+  - **`@getvitops/emdash`: per-item colour.** The rows of `vitops_cards`, `vitops_stats`, `vitops_steps` and the hero's `cards` take their own `tone` / `color` (blank inherits the block's), so one block can hold a pine item and an amber one. Hero cards also take an `eyebrow` and a button (`ctaLabel` / `ctaHref`; with a button the card is no longer a stretched link).
+  - **`@getvitops/generator` / `@getvitops/emdash`: solid fills read.** The generator emits `--color-<hue>-<step>-on` for every step of every hue, the foreground for a fill at that step picked by the same APCA rule as `text-on-<role>` (css and tailwind formats, a plain `:root`, not `@theme`). A block fill chosen by `color` (hue and step) uses it instead of a fixed white..
+  - **`@getvitops/core`: `.counter__value.sr-only`** hides itself, so a build that never emitted the `.sr-only` utility no longer shows a counting figure twice (all formats).
+  - **`@getvitops/astro` / `@getvitops/core`: `SiteFooter` groups.** A top-level item of the `footer-sitemap` menu with children becomes a column (its label is the heading, its children the links, one level only); childless items stay in the flat list. Each column is a named `<nav>`.
+  - **`@getvitops/astro`: planned links and header buttons.** A menu item with `draft` in its CSS classes stays in the menu but is not rendered (at every level, in the header and the footer). `<SiteNav>` has an `actions` slot for header buttons that are not menu items, and an item with `cta` in its CSS classes renders as a button.
+  - **`@getvitops/cli`: `check-prerender` warnings** (fail with `--strict`): links to pages the build did not produce, a form with no delivery address (no `site.notifications.email`, location `email` or `site.crm`), and form fields missing from every `site.templates` form entry (the generated privacy policy reads those). It reads `./site.json`, or `--site=<path>`. `vitops setup … --dry-run` is accepted as `--dry`.
+  - **`@getvitops/emdash` / `@getvitops/astro`: "tick any number" form field** (`vitops_form` field kind `checkboxes`): a fieldset of checkboxes sharing one name. The conversion route joins repeated values (`IT, Marketing`) instead of keeping the last. The "required" toggle is not applied to the group (HTML cannot require one of several).
+  - **`@getvitops/core`: size hooks.** `.steps__title`, `.stats__figure` and `.card__title` read `--steps-title-size` (default one step below `heading`), `--stats-figure-size` and `--card-title-size`, set on the block through its `style` field. They set the `--heading-fs` / `--display-fs` properties the type-role utilities already read, so no extra class or prop is needed (all formats).
+  - **`@getvitops/create`:** the template's `site.json` lists its contact form under `site.templates`, so the privacy policy inventory and the new check agree.
+  - **`@getvitops/emdash`: `theme` on every block, on widget areas and on your own markup.** A `theme` select (`<role>` tinted, `<role>:solid` filled, populated from the site's roles by a new `themes/list` route) is a common field on every `vitops_*` block, applied to the block's own root with the role's computed readable text. `<VitopsWidgetArea theme="…">` takes the same, and `themeAttrs('surface')` gives `{ class, style }` for a layout `<body>`. `vitops_section`'s existing `theme` now goes through the same path.
+  - **`@getvitops/cli` / `@getvitops/emdash`: pages with a dropped block fail the build.** `vitops_section` and widget areas emit an invisible `<template data-vitops-unrendered="…">` for any body block with no renderer, and `check-prerender` fails the page naming the types (nested bodies only; `vitops emdash build` also scans the build log, which covers top-level bodies). A regression test imports the plugin entry first with a mock of the real virtual module, so the old import cycle fails it.
+  - **`@getvitops/emdash`: `formTemplateFromBlock(block)`** turns a saved `vitops_form` value into a `site.templates` form entry (names as submitted, a `checkboxes` field as a `checkbox` with options), to paste into `site.json` so the generated privacy policy lists what the form collects. The build cannot read the CMS database, so this is run by hand; `check-prerender` warns when fields are missing.
+  - **`@getvitops/utils`: `hasFormDelivery`** (`@getvitops/utils/notify`): the one test for "has this form anywhere to go", used by `check-prerender`.
+  - **`@getvitops/emdash`:** a `color` hue tint now flips with the colour scheme (`light-dark()`); hero option cards sit at `h2` under an `h1` hero; menu items also accept `hidden: true` (same as the `draft` class); `vitops docs blocks` documents `theme`, the per-row colours, the `--<role>-fs` type-size hook and the form checks.
+  - **`@getvitops/create`:** the template redirects `/home` to `/`, and the guides use `vp exec` instead of `vpx`.
+
 ## 8.3.0-alpha.1
 
 ### Patch Changes

package/css/patterns/card.css

@@ -33,3 +33,9 @@ wc-cards {
 [data-card-link] {
   cursor: pointer;
 }
+
+/* A card's title keeps the heading role's size unless `--card-title-size` is set on the block
+   (its `style` field). The role utility reads --heading-fs; `inherit` passes through the site's. */
+.card__title {
+  --heading-fs: var(--card-title-size, inherit);
+}

package/css/patterns/counter.css

@@ -17,6 +17,11 @@
  * `display: none`/`visibility: hidden` stops contributing to the accessible
  * name, and that name must read the final value for the whole animation, not
  * just at rest.
+ *
+ * The visually-hidden rule is restated here for `.counter__value.sr-only` rather than left to the
+ * utility: a site whose build does not emit `.sr-only` (the tailwind format only generates
+ * utilities it sees used, and does not scan packages) would otherwise show the figure twice
+ * while it counts, once as text and once as the animation.
  */
 @property --_n {
   syntax: '<number>';
@@ -28,6 +33,18 @@
   display: none;
 }
 
+.counter__value.sr-only {
+  position: absolute;
+  inline-size: 1px;
+  block-size: 1px;
+  margin: -1px;
+  padding: 0;
+  overflow: hidden;
+  clip-path: inset(50%);
+  white-space: nowrap;
+  border: 0;
+}
+
 wc-counter[running] .counter__presentation {
   display: inline;
   animation: counter-run var(--counter-duration, 1.2s) var(--counter-easing, var(--custom-ease-out))

package/css/patterns/logos.css

@@ -6,6 +6,9 @@
  * Each item is a plain image, or a link around one. Marks are normalised to a common
  * height rather than a common width, because logos vary far more in aspect ratio than
  * in how tall they should read. `--grayscale` quiets them until hover or focus.
+ *
+ * An entry with no image is its name set as text (`.logos__name`): a partner without a wordmark
+ * still belongs in the row. The name is sized from the same `--logos-height` so it reads as a mark.
  */
 .logos {
   display: flex;
@@ -30,6 +33,23 @@
     object-fit: contain;
   }
 
+  .logos__name {
+    font-size: calc(var(--logos-height, 2.5rem) * 0.55);
+    line-height: 1.1;
+    font-weight: 600;
+    text-align: center;
+    text-wrap: balance;
+  }
+
+  &.logos--grayscale .logos__item .logos__name {
+    opacity: 0.7;
+    transition: opacity 0.2s;
+  }
+
+  &.logos--grayscale .logos__item:is(:hover, :focus-within) .logos__name {
+    opacity: 1;
+  }
+
   &.logos--grayscale .logos__item img {
     filter: grayscale(1);
     opacity: 0.7;

package/css/patterns/sitenav.css

@@ -536,7 +536,7 @@
   }
 }
 
-/* ── In-page menu (`vitops.nav` block) ─────────────────────────────────────────
+/* ── In-page menu (`vitops_nav` block) ─────────────────────────────────────────
  *
  * A menu read in the body of a page — a site map, a section's links, footer-style columns —
  * as plain nested lists. No disclosure and no drawer: that is the header's job (`.sitenav`).
@@ -613,6 +613,14 @@
   }
 }
 
+/* Header buttons that are not menu items (`<SiteNav><a slot="actions" class="cta">…`). */
+.sitenav__actions {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 0.5rem;
+}
+
 /* ── Footer (`<SiteFooter>`) ───────────────────────────────────────────────── */
 .sitefooter {
   margin-block-start: var(--space-2xl, 3rem);
@@ -639,6 +647,16 @@
   gap: 0.25rem 1.25rem;
 }
 
+.sitefooter__heading {
+  margin: 0 0 0.5rem;
+}
+
+/* A column from a menu item with children: a heading over a stacked list. */
+.sitefooter__list--column {
+  flex-direction: column;
+  gap: 0.125rem;
+}
+
 .sitefooter__link {
   color: inherit;
   text-decoration: underline;

package/css/patterns/stats.css

@@ -34,6 +34,9 @@
   }
 
   .stats__figure {
+    /* Display size by default; --stats-figure-size on the block overrides it (the role utility
+       reads --display-fs). `inherit` passes through whatever the site set for the role. */
+    --display-fs: var(--stats-figure-size, inherit);
     color: var(--tone-fg, inherit);
     font-variant-numeric: tabular-nums;
   }

package/css/patterns/steps.css

@@ -69,6 +69,13 @@
   .steps__text {
     margin: 0;
   }
+
+  /* A step title is a sub-heading, not a section heading: one notch down from the role's size.
+     Set --steps-title-size on the block (its `style` field) to change it. The role utility reads
+     --heading-fs, so this sets the property it already consumes rather than fighting its layer. */
+  .steps__title {
+    --heading-fs: var(--steps-title-size, var(--text-l, 1.2rem));
+  }
 }
 
 /* Side by side once there is room: the marker sits above its text and the line runs across. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getvitops/core",
-  "version": "8.3.0-alpha.1",
+  "version": "8.3.0-alpha.3",
   "description": "The Vitops design-system framework — CSS partials, Lit web components, and browser polyfills.",
   "homepage": "https://docs.vitops.ca",
   "bugs": "https://github.com/getvitops/design-system/issues",
@@ -29,7 +29,7 @@
     "access": "public"
   },
   "devDependencies": {
-    "@getvitops/utils": "8.3.0-alpha.1",
+    "@getvitops/utils": "8.3.0-alpha.3",
     "@lit-labs/signals": "^0.3.0",
     "@oddbird/css-anchor-positioning": "^0.9.0",
     "@oddbird/popover-polyfill": "^0.7.0",