@taprootio/site-authoring 0.1.0 → 0.1.1

package/README.md

@@ -223,12 +223,18 @@ Actions output.
 
 ## Public release
 
-Private Taproot is the source authority. A private `site-authoring-v<version>`
-tag verifies this package — the release commit must belong to `main`, the tag
-must name the version `package.json` declares, and `@taprootio/espalier` must
-be pinned to the exact version the release manifest records — then
-allowlist-exports only `packages/site-authoring/` to public
-[`taprootio/trunk`](https://github.com/taprootio/trunk). Trunk's separate
+Private Taproot is the source authority. Merging a version bump to private
+`main` releases this package: the release workflow verifies that the commit
+belongs to `main`, that `site-authoring-v<version>` names the version
+`package.json` declares, and that `@taprootio/espalier` is pinned to the exact
+version the release manifest records, then allowlist-exports only
+`packages/site-authoring/` to public
+[`taprootio/trunk`](https://github.com/taprootio/trunk), whose commit and
+`site-authoring-v<version>` tag are the release record and name the private
+source commit. A pull request that changes this package's public files
+without raising the version fails CI, so the bump is never an afterthought;
+pushing a private `site-authoring-v<version>` tag by hand remains the manual
+path and runs the same verification. Trunk's separate
 `publish-site-authoring.yml` workflow tests and publishes those exact public
 tag bytes with npm trusted-publishing provenance, under its own concurrency
 group, GitHub Environment, tag prefix, and npm identity.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taprootio/site-authoring",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Taproot site authoring CLI: sign in once in the browser, then pull, validate, push, preview, approve, and deploy a site from the terminal",
   "type": "module",
   "license": "ISC",
@@ -27,7 +27,7 @@
     "README.md"
   ],
   "dependencies": {
-    "@taprootio/espalier": "4.4.0"
+    "@taprootio/espalier": "4.6.0"
   },
   "scripts": {
     "test": "node --test",

package/src/constants.js

@@ -1,5 +1,5 @@
 export const CLI_NAME = "@taprootio/site-authoring";
-export const CLI_VERSION = "0.1.0";
+export const CLI_VERSION = "0.1.1";
 export const CLI_BINARY_NAME = "taproot-site";
 export const RESULT_SCHEMA_VERSION = 1;
 export const CONFIG_FILE_NAME = "taproot-site.json";

package/src/content/components.js

@@ -227,6 +227,9 @@ const IMAGE_BANNER = Object.freeze({
   }),
   ratio: enumOf("4/1", "3/1", "2/1"),
   compactRatio: enumOf("", "2/1", "3/2", "1/1"),
+  // `ratio` keeps the wide/compact shape, capped at the viewport space below
+  // the site header; `viewport` fills exactly that space (TR00413).
+  heightMode: enumOf("ratio", "viewport"),
   contentPosition: enumOf("bottom-start", "bottom", "bottom-end", "center", "top-start", "top", "top-end"),
   scrim: enumOf("auto", "none", "flat", "top", "bottom", "left", "right", "radial"),
   scrimStrength: enumOf("soft", "medium", "strong"),
@@ -457,6 +460,7 @@ const COMPONENT_DEFINITIONS = Object.freeze({
       focus: { x: 0.5, y: 0.5 },
       ratio: "3/1",
       compactRatio: "3/2",
+      heightMode: "ratio",
       contentPosition: "center",
       scrim: "auto",
       scrimStrength: "medium",
@@ -473,6 +477,7 @@ const COMPONENT_DEFINITIONS = Object.freeze({
       altText: "",
       overlayText: "Train together",
       focus: { x: 0.5, y: 0.35 },
+      heightMode: "ratio",
       contentPosition: "bottom-start",
       scrim: "bottom",
       scrimStrength: "medium",

package/src/presentation-reference.js

@@ -271,6 +271,7 @@ export function getThemeReference() {
       "Define brand anchors first, then assign canvas, ink, accent, action, and structure roles in both schemes.",
       "Add named contexts for whole zones, including inverted zones, and rebind lightness when the zone changes brightness.",
       "Tune typography, type/space ratios, radii, and viewport interpolation as one layout system.",
+      "Typography is per scheme on purpose: light and dark set their own moods, so a heading, body, or brand face that differs between them is a design choice, and theme push never warns about it.",
       "Retune danger/success/warning/info through intents without changing their meanings; design data palettes separately.",
       "Use semanticMappings only for meanings roles and contexts cannot express; scattered pins shadow the coherent model.",
       "Run theme push, inspect warnings, then verify text, actions, focus states, and both schemes in authoring previews.",

package/src/reference-help.js

@@ -27,7 +27,7 @@ import {
 
 export { getAppearanceReference, getFooterReference, getThemeReference };
 
-export const REFERENCE_VERSION = 13;
+export const REFERENCE_VERSION = 15;
 export const PAGE_TYPES = Object.freeze(["free-form"]);
 export const REFERENCE_TOPICS = Object.freeze([
   Object.freeze({ name: "pages", usage: `${CLI_BINARY_NAME} help pages`, summary: "List authorable page types." }),