Blocks Editorial Pack

0.43.x

0.42.x

0.39.xMinor

• info-panel margin facts now land on the page grid's lanes, and the facts band takes a theme column count.

  • Fix: the lanes. The block's root was a block-level box between the wrapper RenderBlocks puts around every block (a subgrid of the page grid) and the section that subgrids it in turn. The section's grid-template-columns: subgrid therefore computed to none, and with factsPlacement: 'margin' the facts, the prose and the sidebar card all fell into one column from 1280px. The root now generates no box of its own (display: contents), so the section is a direct subgrid of the wrapper and the lanes exist. The framed variant (showFrame) keeps a box for its border. Markup is unchanged (the golden test still passes); only layout inside a page grid moves, and only for a block that relies on its named lines.
  • `--tome-info-panel-facts-columns`. The facts band from 1024px to 1279px reads this custom property for its grid-template-columns ("repeat(4, minmax(0, 1fr))"). Unset, it is as many 10rem columns as fit, as before.

  Purely additive in options: no field, peer or default changes.

• info-panel can read the card's person on one line: "Jess, lead coach".

  • personLine: 'inline' (a select with no default, shown with the sticky card) renders a <span data-panel-person-sep>, </span> between the name and the role and marks the text data-person-line="inline", so the name and role share a line.
  • Unset, null or stacked keeps the role under the name; stored documents render byte-identical markup.

  Purely additive: no peer is added or tightened. The new select field adds a column, so a site with migrations generates one.

• info-panel can put the card's person after the button.

  • personPlacement: 'after' (a select with no default, shown with the sticky card) renders the lead person after the call-to-action button, in the DOM as well as on screen, so the reading and tab order match what the eye sees. A theme no longer needs CSS order to place the coach under the button.
  • Unset, null or before keeps the person under the kicker exactly as before; stored documents render byte-identical markup (the golden test still passes).

  Purely additive: no peer is added or tightened, and nothing changes for a site that does not set the field.

• info-panel can put its key facts in the left margin and host a live list in its sidebar card.

  • factsPlacement: 'margin' (a select with no default) moves the key facts out of the sidebar into their own region before the prose, <aside data-key-facts-placement="margin">, each fact reading label over value. The layout is a single column under 1024px, a band of facts above the prose from 1024px to 1279px, and from 1280px the page grid's lanes: facts in the left marginalia, prose in the reading lane, sidebar in the right marginalia. Unset or card keeps the facts in the sidebar exactly as before.
  • The renderer takes a panelSlot prop (a new InfoPanelProps, the same pattern as contact's formSlot). A site passes any node, such as a list of the next sessions, and it renders inside the card in [data-panel-slot], after the person and picture and before the key facts and button. A slot alone is enough to show the card. Omitted, nothing renders.

  Stored documents that set neither render byte-identical markup (pinned by a golden test).

  Purely additive: no peer is added or tightened, factsPlacement has no default, and nothing changes for a site that uses neither.

• info-panel can put a small tag beside a key fact's value and a one-line quote under the card person's role.

  • keyFacts[].note (optional text, localized): a status such as "Illustrative" or "Sample", rendered as <span data-fact-note> after the value text and not inside it. It shows in the sidebar list and in the margin placement.
  • panelPerson.quote (optional text, localized): one line in the person's own words, rendered as <span data-panel-person-quote> under the role and before the note, shown only when the person has a name.

  A block that sets neither renders exactly the markup it did before. Purely additive: no peer is added or tightened.

0.38.x

0.37.xMinor

• annotated-page gains a voice variant, two note kinds and lists in the paragraph editor.

  The voice variant sets an essay: no paragraph numbers, the text on the narrow prose track from 1024px, every note numbered with an anchor numeral at the end of its paragraph, and notes placed under their paragraph until 1280px and in the right margin from 1280px. It adds a kicker label, a deck (one sentence under the heading, data-block-deck), a dropCap checkbox and a footnotesLabel, and marks the root with data-reading-body for reading-time counters.

  Its layout is a stylesheet shared with the essay body of a post, and with a drop cap the first paragraph of the first row with text carries data-drop-cap-target. Type [^*] in a paragraph to place a footnote's mark where it is typed.

  New hooks: data-annotated-part, data-note-number, data-fn-marker, data-footnotes, data-footnotes-label, data-footnote, data-footnote-mark, data-lane-kicker, data-drop-cap, data-notes-from.

  New note kinds exercise (for a "Try this" prompt) and footnote (a symbol mark in the text, collected into a list after the last paragraph) work in both variants. The paragraph editor now offers ordered and unordered lists.

  Existing pages and the default variant render exactly as before.

• New ./essay entry sets a post in the Margin Voice, so an essay can be a Post and an editor works in the post editor.

  • marginNoteBlock: a margin-note Lexical block for a post body (kind with every note kind including exercise and footnote, label, body, person, and an optional citationNumber). A note attaches to the paragraph, list, heading or quote just above it; the admin says so.
  • EssayBody: groups a post body into voice rows and renders them with the same row renderer as the annotated-page voice variant. An h2 opens a part, every note is numbered 1 to n in reading order with its anchor appended to its row, footnotes get symbol marks and an end list, and the drop cap comes from a post field. Uploads, banners and other blocks go to a renderNode callback. It emits data-essay-body, data-reading-body and the shared voice hooks, and it ships the layout itself: notes in the right margin from 1280px and inline below, text on the prose track, with the same stylesheet annotated-page voice uses (one source, mounted by EssayBody through <BlockStyles>), so a template imports no CSS.
  • essayPostFields(): the essay field group for a Posts collection (kind, revised date, "In short" summary, drop cap, running head on or off), shown for the ESSAY design version.
  • MarginNoteInline: a note in the flow of the text, for a post template with no margin. marginNoteFallback() reads a stored note as plain data for a serializer that cannot import the pack.
  • Footnote placement: type [^*] in a paragraph and the next footnote note's mark lands there instead of at the paragraph's end; footnotes with no token keep the end mark. It works in annotated-page too.
  • essayReadingMinutes(): reading time with margin-note text included, from core's reading-time rule.

  The entry has two halves, ./essay/config (loads the Lexical editor runtime) and ./essay/render (no Payload runtime; EssayBody mounts its layout stylesheet), and ./essay joins both. @wabbit/tome-core becomes a required peer (>=1.23.0 <2.0.0) for the reading-time rule.

  The margin-note block turns off the editor's block-name input, which duplicated the label. Existing blocks and exports are unchanged.

• Updated dependencies [d69161c]

  • @wabbit/tome-ui@0.20.0

0.36.xMinor

• info-panel can hide the key-facts heading, and wraps each section sign in the section label in a data-section-label-mark span.

  The new showKeyFactsLabel checkbox (default on) shows or hides the heading above the key facts; content that never set it keeps the heading. Hidden, the facts sit in a role="group" whose aria-label is the key-facts label.

  A § or ¶ in the section label, linked or not, gets its own <span data-section-label-mark="">, so a theme can color the sign; text and accessible name are unchanged.

0.35.x

0.34.xMinor

• info-panel can open a page, and its section label can leave mono.

  • The main rich text allows h1 (it allowed h2 to h4), so a panel that heads a page can carry the page's h1. The prose rhythm styles h1 with the other headings. Existing content is unchanged.
  • The section label's voice is tokenised: --tome-info-panel-label-font (font family, default the mono face), --tome-info-panel-label-case (text-transform, default uppercase), --tome-info-panel-label-tracking (default the widest tracking) and --tome-info-panel-label-caps (font-variant-caps, default normal). A theme can set the label in small caps. The label carries data-section-label.
  • New optional sectionLabelLink.text: the label's leading part to link. With "Practice" on "Practice · Leases", only "Practice" is the link (data-section-label-link) and " · Leases" follows as <span data-section-label-rest>. Empty, or text the label doesn't start with, links the whole label as before.

0.32.xMinor

• A new Annotated Page block, plus a person note, photo-or-initials tile and linkable section label on the Info Panel.

  • Annotated Page (annotated-page, new): rows of prose, each with an automatic paragraph number and its own margin notes. Fields: an optional heading and rows[] { subheading?, body, notes[] }, where each note is { kind, label?, citationNumber?, person? { name, initials, role }, body? } and kind is note, person, citation, fee, timeline, jurisdiction or reviewed. From 1024px the number sits in the left margin and the notes in the right margin, each row its own subgrid so a note lines up with its paragraph without JS; from 768px the notes move to the right margin; below 768px each note follows its paragraph inline. To cite a note, type [^n] in the paragraph and give a citation note citationNumber: n: the token renders as a superscript link to the note (data-cite-marker), and the note's number links back. A person note needs no photo (an initials tile). Theme hooks are listed in the README.
  • Info Panel: panelPerson gains an optional note (a small line under the role, data-panel-person-note) and an optional photo; without a photo the tile shows the initials and now also carries data-panel-initials. A new optional sectionLabelLink { href } turns the section label into a link (data-section-label-link). A new panelPosition select (sticky, the default, or static; shown with stickyPanel on) lets the card stay in place without sticky positioning; the sidebar then carries data-panel-position="static". stickyPanel is effectively the switch that shows the card; it will be renamed in the block's next breaking version.

  All new fields are optional. Existing content renders as before.

0.31.xMinor

• Phase Ledger outcome hooks, an Info Panel card kicker, and two-column margin facts on phones.

  • Phase Ledger (dossier): each phase's outcome line carries data-phase-outcome, and its italic and weight read --tome-dossier-phase-outcome-style (default italic) and --tome-dossier-phase-outcome-weight (default 330), so a theme can restyle the outcome without overriding the declarations. The look is unchanged when neither token is set.
  • Info Panel (editorial): the sticky panel card gains an optional panelKicker, a small label rendered first in the card, above the person (hook data-panel-kicker). It is read only with stickyPanel on, and a kicker alone is enough to render the card. The person's name may now be a full lead sentence ("Marisol Vance leads roof replacements."), with role as the sentences that follow. Both wrap beside the initials with no clamp or truncation, and the admin label and descriptions say so. Set initials when the name is a sentence.
  • Editorial Spread (editorial): margin facts (rail.statCallouts that carry a note) sit in two columns on phones (under 640px) instead of one long column. An odd last fact sits alone in the first column. Tablets keep the auto-fill columns, and the desktop rail is unchanged.

  Existing content renders as before.

• Updated dependencies [1767d0d]

  • @wabbit/tome-ui@0.18.0

0.30.xMinor

• info-panel with a sticky sidebar takes optional panelPerson, panelMedia and panelCta, rendered as one card: person, media thumb, key facts, then a button.

  The fields show only for the Prose + Sidebar treatment with Sticky Sidebar on. Person initials default to the first and last name.

  Theme hooks: data-panel-card, data-panel-person, data-panel-person-initials, data-panel-person-name, data-panel-person-role, data-panel-media, data-panel-cta. With none set, the panel renders as before.

  The panel's rich text now has paragraph spacing, heading rhythm and list markers in the block's own stylesheet, so lists and paragraphs read correctly under a CSS reset.

0.29.xMinor

• editorialSpread rail stat callouts take an optional note, rendered under the label in small muted type, so the rail can carry "margin facts" (value, label, note).

  Migration: this adds a field to the editorialSpread block, so run your Payload migration (payload migrate:create, then payload migrate on SQL databases) and regenerate your Payload types after upgrading. Existing spreads render unchanged.

  rail.statCallouts[].note is a localized text field capped at 120 characters. Below lg, where the rail collapses to an eyebrow and hides its details, stat callouts that carry a note now stay visible as a compact, hairline-separated list on their own row; bare value-and-label stats still collapse as before.

  Theme hooks: [data-rail-facts] on the list (with data-has-notes="true" when any note is set), [data-rail-fact] on each item and [data-rail-fact-note] on the note. The rail-right demo now shows margin facts.

0.28.x

0.27.x

0.26.x

0.23.xMinor

• Breaking: block stylesheets are now per-block (`.tome-css`). Each block's CSS ships only on pages that render it, instead of in every page's CSS bundle.

  The 12 stylesheets moved from X.module.css to X.tome-css, and each renderer renders <BlockStyles sheet={styles} /> from @wabbit/tome-blocks-core/block-styles.

  Required in the consuming site: wrap next.config with withTomeBlockStyles (@wabbit/tome-blocks-core/next, blocks-core 0.22.0 or later); without it the .tome-css imports fail to build. See the blocks-core README, "Per-block stylesheets".

  • The @wabbit/tome-blocks-core peer range is now >=0.22.0 <1.0.0.
  • EditorialSection and EditorialSpread are client components; each is now a server-safe wrapper (X.tsx) around X.client.tsx. Exported names and props are unchanged.
  • Block CSS now loads after all bundled CSS. A site-level rule that overrode one of this pack's classes at equal specificity, and won only by loading later, no longer wins.

0.20.x

0.18.x

0.17.xMinor

• Tome block packs now install into an existing Payload project the way the README says: one npm install, one CSS import, no undocumented steps.

  Proven by the new fresh-install smoke test (scripts/blocks-fresh-install-smoke.mjs) against a brand-new create-payload-app website-template site.

  Consumers: list `@wabbit/tome-blocks-core` and `@wabbit/tome-ui` in your own `package.json` if you import from them (npm 7+ and pnpm install required peers automatically, so a fresh npm install of a pack already brings them in).

  • One shared `blocks-core` per site. Every pack, blocks-house and blocks-extras now declare @wabbit/tome-blocks-core (and, where used, -house / -extras) as a required peer with an explicit range instead of a regular dependency, so a site gets exactly one hoisted copy and one adapter registry.
  • No more ERESOLVE in plain Payload sites. blocks-core no longer declares @wabbit/tome-core or @wabbit/tome-catalog (their optional peer graph pulled better-auth → @sveltejs/kit → vite@8 against a site's vite@7). The block-bundle product type still auto-registers when both are installed; new structural types BlockBundleProductTypeDeps, BlockBundleProductTypeRegistryLike, RegisterProductTypeHooksLike.
  • Tokens in one line: @import '@wabbit/tome-blocks-core/styles.css'; (new export; imports @wabbit/tome-ui/tokens). @wabbit/tome-ui is now a required peer of blocks-core.
  • Rich text and images render with no adapter setup. Built-in defaults render Lexical through @payloadcms/richtext-lexical/react and resolve populated Payload uploads; an unpopulated upload id warns once in every environment (previously content vanished silently in production). Registered adapters still win.
  • Payload's spread-props convention: new adaptRenderersForPayload(renderers) / adaptRendererForPayload(Component) wrap any pack's renderers map for a site that renders <Block {...block} />.
  • Slug collisions with Payload's templates (cta, banner, archive, content, code): new applyBlockSlugOverrides(blocks, overrides) and remapRendererSlugs(renderers, overrides) (@wabbit/tome-blocks-core/slugOverrides). Defaults are unchanged; no stored data migrates.
  • `blocks-house` owns gsap and hls.js as dependencies (previously optional peers that still broke the build when missing), and registers GSAP's ScrollTrigger itself before first use.
  • Full-bleed bands actually span the grid. Eight pinnedBand blocks (cinema-pack AmbientBand, MediaPanel, PullInterlude, SceneCaption, ScenePlate, ScrubStory, StatementBand; blocks-house FullBleedInterstitial) now declare grid-column: 1 / -1 at their root as the contract requires. Visible change: inside a tome-ui .grid, these render edge to edge where they were previously squeezed to content width.
  • `@wabbit/tome-ui`: .grid declares reading-start / reading-end below 768px (aliased to the content column), so blocks placed on the reading column no longer collapse to a sliver on phones.
  • Every pack README gains an "Install into an existing Payload project" section and a peer table that matches package.json; blocks-core's README carries the full walkthrough.
• Updated dependencies [404d325]

  • @wabbit/tome-ui@0.13.1

0.16.xMinor

• Raise the react / react-dom peer floor to >=19.0.0 across the linked blocks family.

  Every pack advertised react: >=18.0.0 while @wabbit/tome-core, chrome, forms, dispatch, longform and readout all require >=19 — so the React 18 support the packs claimed was unreachable in any real Tome stack: no consumer could satisfy both halves of the graph. The advertised range was not a supported configuration, it was a range nobody could install into.

  Ruled 2026-09-01: the floor becomes the truth.

  Their devDependencies said the same thing from the other direction: react and @types/react pinned to ^18.0.0 while the root pnpm.overrides has pinned @types/react to 19.2.14 for months, so every pack has in fact been developed and tested against React 19 types the whole time. Those pins move to ^19.0.0 — a manifest correction, not a version change; the resolved tree is byte-identical.

  One coordinated bump for the family (these eleven are linked in .changeset/config.json, so they version together by design).

  Consumer impact: a consumer genuinely on React 18 can no longer install these packs. That consumer could not have had a working Tome install anyway — the kernel would have refused the same graph.

  Anyone on React 19 sees no change.

• dist now raw-Node loadable: relative specifiers get explicit extensions post-build.

  build gains && node ../../scripts/fix-dist-extensions.mjs --strict as its last step, joining the 13 packages that already ran it. tsup builds bundle: false and emits relative specifiers exactly as the TypeScript source wrote them — extensionless — which bundlers resolve and raw Node does not (ESM ERR_MODULE_NOT_FOUND; CJS worse, require('./x') finds the ESM .js twin and Node 22+ require(esm) then dies on that file's own extensionless import). Every consumer outside a bundler hit this: the payload CLI under plain node, generate:types, generate:importmap, ops scripts, codegen tools.

  No source changes, no API changes, and bundler consumers are unaffected — extensioned relative specifiers are universally resolvable.

  Two supporting changes made the wiring possible, both in repo scripts rather than package source. fix-dist-extensions.mjs now skips bundler-asset specifiers (.css, .module.css, .scss, fonts, images, shaders) by explicit extension allowlist instead of reporting them as unresolvable — that single gap is why the 13 prior adopters were exactly the 13 packages that ship no CSS, since --strict exited 1 on any package with a relative stylesheet import.

  Dotted MODULE names (./config.meta, ./x.variants, ./y.demo) are deliberately NOT treated as assets and still get .js/.cjs appended. assert-node-loadable.mjs gained the matching carve-outs so the new repo-wide CI gate reports real defects only: a resolution failure whose path lands under node_modules is a peer SKIP (next@15 has no exports map, so next/image fails as an absolute path), and a bundler-asset load failure is an environmental SKIP (CJS surfaces it as SyntaxError: Unexpected token '.' raised from inside the stylesheet).

  Verified before/after on four packages built one at a time: print 8 FAIL → 0, readout 22 FAIL → 0, ai 3 FAIL → 0, gamification 2 FAIL → 0 (its failure was the other signature — a directory import missing /index). cop was already clean on a fresh build, so the audit's "27 of 46 fail" figure includes at least one package whose local dist was merely stale.

• Manifest metadata: homepage, bugs, engines.

  All 46 publishable manifests were missing the three fields a consumer sees before any code (2026-09-01 sale-readiness audit §6). Metadata only — no source, no build, no runtime change.

  • homepage deep-links to that package README on GitHub (.../tree/main/packages/<dir>#readme). Without it a registry page links to the monorepo root and the reader has to guess which of 46 folders they want.
  • bugs.url points at the repo issue tracker, so a paying customer has a place to report a defect that is not email.
  • engines.node is >=22, matching the root engines and .nvmrc set the same day. This is a real floor, not decoration: CI on Node 20 could not expand the glob the block packs use for node --test, and a package installed on Node 20 fails at a runtime the installer cannot connect back to the version.

  The forcing function ships with the change: scripts/assert-manifest-metadata.mjs (root pnpm assert:manifest-metadata, wired into platform-discipline.yml beside assert:license-metadata) fails when any publishable manifest lacks description, repository.directory matching its own folder, homepage, bugs, engines.node equal to the repo floor, license, files or sideEffects. It reported 138 violations before this change and 0 after.

• Fix a hydration mismatch in Testimonial and adopt the shared UTC-pinned date formatter across five renderers.

  @wabbit/tome-blocks-marketing-starter's Testimonial is a 'use client' component and rendered its publication date with a bare new Date(iso).toLocaleDateString(). That resolves against the RUNTIME locale and the RUNTIME time zone, so the server produced one string and the browser produced another and React reported a hydration mismatch on the block.

  The 2026-07-11 audit flagged it; it was still there on 2026-09-01.

  The same bare call sat in four server renderers — blocks-editorial-pack's MetricStrip and StatusBoard, blocks-agency-essentials' TeamRoster (twice) and Timeline. No hydration mismatch there, but the rendered output changed with the deploy host's locale and offset, which is its own kind of wrong.

  All six call sites now use formatDisplayDate from @wabbit/tome-blocks-core/utilities/formatDisplayDate with an explicit locale: 'en-US', a numeric M/D/YYYY dateStyle and timeZone: 'UTC'. The numeric shape is deliberate: it is byte-identical to what a US-locale runtime already produced, so this fixes the determinism without silently restyling anyone's dates.

  Every pack already declared @wabbit/tome-blocks-core, so no dependency changes.

  Shipped with its forcing function: a no-restricted-syntax rule in eslint.config.mjs warns on bare toLocaleDateString/toLocaleString/toLocaleTimeString in every packages/*/src/**/*.tsx and every block pack's render/ directory, and points at formatDisplayDate and at blocks-gallery's ADDED_AT_FORMATTER as the two accepted shapes.

• README peer tables, and the gate that now requires them.

  Sixteen packages declared peerDependencies and documented them nowhere a reader could scan — in prose inside an install paragraph, in a transposed "compatibility matrix" with the peers as columns, or not at all. Docs only; no source, no manifest, no runtime change (the one manifest change in this PR, admin's sonner peer, has its own changeset).

  Each of the sixteen gains a ## Peer dependencies section generated from its own package.json — | Peer | Range | Required |, one row per peer, the range verbatim, no (optional) read from peerDependenciesMeta, plus one sentence on what is a real dependency rather than a peer and why the optional ones are optional. The worst omissions this surfaced: @wabbit/tome-core documented 2 of its 13 peers and left out both next and @payloadcms/richtext-lexical, which are required; @wabbit/tome-admin listed 5 of 20; @wabbit/tome-readout and @wabbit/tome-sc listed none.

  Eight block packs carried a hand-typed compatibility table that had drifted a full React major — still >=18 after the peer floor moved to >=19.0.0 — and none of the eight listed react-dom at all. Those tables are retired in favor of the generated one, with a line saying what they used to claim so the next reader does not reinstate them.

  The forcing function ships with the fix: scripts/assert-readme-contract.mjs now FAILS a package that declares peers without a peer table (a markdown table whose header row names a Peer and a Range column — the existing Optional? and Notes third columns still pass, so the thirty already-conforming READMEs were not touched). It is deliberately shape-only, not row-level: asserting that each row agrees with the manifest is the Tier 2 generation work.

  Verified non-vacuous by breaking one table's header and watching the gate fail, then restoring it. CONTRIBUTING.md's assert-script list — which said "five" while sixteen existed — and the three guides that describe this gate were corrected in the same pass.

• Updated dependencies [57875ba]

• Updated dependencies [b01ca1f]

• Updated dependencies [0836ef5]

• Updated dependencies [73081e6]

• Updated dependencies [b01ca1f]

• Updated dependencies [090e984]

• Updated dependencies [73081e6]

  • @wabbit/tome-blocks-core@0.16.0
  • @wabbit/tome-blocks-extras@0.16.0
  • @wabbit/tome-ui@0.12.0

0.15.xMinor

• Route pack block links through the LinkAdapter instead of raw <a href>.

  LinkAdapter (0.14.0) shipped the seam; this connects it. 67 anchors across 55 renderer files in 10 packs now render through <TomeLink>, so a consuming site that registers a link adapter gets its route transition on pack blocks — previously impossible by construction, since a pack cannot import the consumer's transition component and the consumer cannot reach into a pack's render tree.

  New in `@wabbit/tome-blocks-core`: `<TomeLink>`, a component form of resolveLink(). resolveRichText() / resolveMedia() are functions because they turn a data value into content; a link _wraps children_, and the function form forces multi-line JSX through a children: prop.

  <TomeLink href={…}>…</TomeLink> is a drop-in for the <a> it replaces. It delegates to resolveLink(), so there is exactly one resolution path, and it stays directive-free so RSC pack renderers can use it without becoming client components.

  `LinkProps.href` is now `string | null | undefined`. Block data routinely carries an optional URL, and the raw <a href={undefined}> these calls replaced was legal markup. Narrowing it to string would have forced ~10 non-null assertions across the packs and changed behavior at each.

  NOOP_LINK_ADAPTER normalizes null to undefined so React omits the attribute — the unregistered path stays byte-identical to the pre-adapter markup.

  Behavior is unchanged for every consumer that has not registered a link adapter, which is currently all of them: resolveLink falls back to a plain <a>.

  Deliberately left as raw <a>:

  • EditorialFootnotes — its #fnref-* anchors are in-page backlinks. Client-routing them would play a page transition for a jump within the same document.
  • PricingPlans / PricingPlanCard — these already accept an injectable anchor component, a more expressive consumer mechanism that predates the adapter.
  • LogoSlider — a self-closing, childless target="_blank" overlay anchor. Always external, so the adapter would hand it straight back to the browser.
  • @wabbit/tome-longform — it has zero runtime dependencies and does not peer on blocks-core. Adding that edge to the layer graph is its own decision, not a sweep side effect.
• Updated dependencies [510036f]

  • @wabbit/tome-blocks-core@0.15.0
  • @wabbit/tome-blocks-extras@0.15.0

0.14.x

0.13.xMinor

• feature: walk-strip + ledger-dark variants graduated from tome-starter (showcase Phase 3.7); manifest variant registered (closes doc/code drift — the variant array was missing an entry the doc comment and designVersion picker already described); note + columnSpan + USPs link added to the base schema.

  manifest is style-only, no schema change: it's the FEATURE_COP3 layout registered under its _variant slug, with a non-breaking fallback in the renderer (block._variant === 'manifest' applies the FEATURE_COP3 style class only when no legacy designVersion is set — existing FEATURE_COP1/2/3 documents render exactly as before). walk-strip is numbered stop cards — mono counter, serif stop title, body, and a real route link per stop, staggered offsets, scroll-reveal via @wabbit/tome-blocks-core's Reveal helper; its per-USP link group lives on the base schema behind an admin.condition (not a fieldOverrides schema variant, same rationale as the cta door variants) using a newly-ported createBlockItemCondition helper (src/shared/blockItemCondition.ts, adapted from tome-starter's findParentFeatureVersion to not assume a hardcoded blocks-field name, since this package is consumed by sites that name it differently).

  ledger-dark is the ink full-bleed stat band — serif numerals with an accent superscript (a USP tagline of "96 free" splits into "96" + superscript "free"), mono uppercase labels over hairline rules, and a ruled note row (Ledger Dark only, behind an admin.condition on _variant); seed with columnSpan: '1 / -1' for full bleed.

• Updated dependencies [f4d55c9]

• Updated dependencies [eb403d4]

  • @wabbit/tome-blocks-core@0.13.0
  • @wabbit/tome-blocks-extras@0.13.0

0.12.x

0.11.xMinor

• EditorialSpread's two rail-rendering copies (RailInternals vs the rail-both left-rail IIFE) had silently drifted in field order — links-vs-statCallouts rendered in different orders per variant.

  Deduplicated into one RailPrimaryContent sub-component normalized to links → statCallouts. VISIBLE CHANGE (hence minor): rail-left/rail-right/rail-top variants that populate BOTH links and statCallouts render them in the new order.

  Worth a glance on live editorial pages using both fields.

• Every package now declares an explicit sideEffects field (38 added; motion/engine/forms already correct).

  Registration-bearing modules (render files' registerRenderer, blocks/*/index.ts defineBlock self-registration, widget register.ts files, productHooks, permission self-registrations, print templates, chrome built-in variants) are listed so bundlers can tree-shake everything else WITHOUT dropping import-time registrations — previously the field was unset, which blocked cross-module tree-shaking through the barrels entirely. Never blanket false on a package with registration or CSS.

• The clientization migration: 127 render components across seven packs dropped 'use client' — every file individually re-verified hook/handler/context-free before stripping; adapter-consuming static blocks converted to resolveRichText/resolveMedia.

  Exactly 20 of 155 renderers remain client, each for a verified reason (state/effects/motion, or a documented client-shell composition contract), enforced by the new assert:rsc-boundaries CI script (per-pack manifest; fails loudly if a directive creeps back or a count drifts). Every renderer-bearing pack now exports ./render/register (renderers map + explicit registerRenderers()), aggregated by @wabbit/tome-blocks's new registerAllRenderers() — the format-safe registration path for server component graphs, where the legacy import-time barrel registration never executes (that legacy path is unchanged and remains supported until the spec's deprecation trigger).

  RenderBlock is rewritten server-safe: directive-free, optional components prop (RenderBlocks parity) → registry fallback, dev warn-once naming both fixes on a miss; its docs state the explicit-registration prerequisite. Rendered output is byte-identical everywhere; behavior change only for consumers rendering migrated blocks in RSC WITHOUT a provider or registration — they get the documented warn + graceful degradation instead of silent client bundling.

• Updated dependencies [26dfa07]

• Updated dependencies [36e537a]

• Updated dependencies [36e537a]

• Updated dependencies [36e537a]

• Updated dependencies [a93f478]

• Updated dependencies [5f78397]

• Updated dependencies [5f78397]

• Updated dependencies [aef2725]

• Updated dependencies [aef2725]

• Updated dependencies [aef2725]

  • @wabbit/tome-blocks-core@0.11.0
  • @wabbit/tome-blocks-extras@0.11.0
  • @wabbit/tome-ui@0.9.9

0.10.x

0.9.xMinor

• layoutGrid nesting capability audit + render hardening (Wave 2).

  Tags the nestable capability flag (and a minColSpan floor for internally-wide blocks) across the offered blocks in the core packs (extras, marketing, content, agency, editorial, signal), so the layoutGrid container's derived child allowlist — blockRegistry.getNestableBlocks() — is populated rather than empty. Excluded by design (left non-nestable): containers (editorialSpread, editorialSection, split-view, stacking-wrapper, grid, layoutGrid) to enforce the one-level depth cap; full-bleed heroes/banners (band-owners); and inline Lexical blocks (not block-level grid children).

  minColSpan: 2 is set on the internally multi-column blocks (card-grid, bento-section, content-two-column, signal-stats, signal-image-grid, signal-data-table) so they cannot be crammed into a single-column cell.

  Also hardens LayoutGrid's child↔span pairing: children are now flattened with null slots preserved (instead of React.Children.toArray, which drops nulls), so an unrenderable child can no longer shift every later child's span metadata onto the wrong block. Adds a dev-mode warning when the consumer's child count doesn't match the item count.

  @wabbit/tome-blocks-core is bumped to release the layoutGrid platform primitives merged earlier but never published (the registry's 0.8.0 predates that merge): BlockMeta.nestable/minColSpan, withChildPlacement, the reserved _colSpan/_rowSpan/_order field constants, and blockRegistry.getNestableBlocks(). Without this, a consumer wiring the layoutGrid allowlist would call a getNestableBlocks that its installed blocks-core@0.8.0 does not have.

  Domain packs (lms, catalog, sc, org) are intentionally deferred — they compose into their own domain layouts and can opt in when a consumer needs them.

• Updated dependencies [c7d0afc]

  • @wabbit/tome-blocks-core@0.9.0
  • @wabbit/tome-blocks-extras@0.9.0

0.8.x

0.7.xMinor

• Expose a client-safe ./demo export (the already-built, payload-free getDemoProps module) on each block pack, separate from the payload-importing root barrel.

  The root barrel (.) eagerly pulls each block's config, which imports payload (→ richtext-lexical → pino → worker_threads). A consumer that registers packs client-side (the wabbit /blocks gallery storefront, B6) can't import getDemoProps from the root barrel without dragging payload/worker_threads into the browser bundle (build failure).

  The dist/demo.* module is already built and contains only demo-data + type imports — this change just makes it importable as @wabbit/tome-blocks-<pack>/demo.

  Additive; no code or runtime change to the packs.

  NOTE: this is the getDemoProps half of the client-safe gallery-registration fix. The companion piece — a client-safe block-meta/descriptor export (slug/label/variants/tier, separate from the payload-importing config the gallery bridges currently read .meta off) — is still needed before B6 can register packs entirely off the root barrel.

  Tracked separately.

• Expose a client-safe ./meta export on each block pack: payload-free block descriptor metadata (slug/name/description/category/tags/source + variants), separate from the payload-importing root barrel.

  This is the companion to the ./demo export. Each block's meta literal is now extracted into a co-located payload-free meta module that the block config imports, and a pack-level ./meta entry exposes the full descriptor list as <pack>BlockMeta.

  A consumer registering packs client-side (the wabbit /blocks gallery storefront, B6) can now read block metadata for gallery entries without importing the root barrel, which eagerly pulls each block's config (payload -> richtext-lexical -> pino -> worker_threads) into the browser bundle.

  Additive and behavior-preserving: defineBlock receives the same meta object (now imported rather than inline); the block registry, configs, demos, and existing exports are unchanged. The pack BlockMeta array is also re-exported from the root barrel for path-alias consumers.

• Updated dependencies [28802fa]

• Updated dependencies [66c611c]

• Updated dependencies [8958d41]

  • @wabbit/tome-blocks-extras@0.7.0
  • @wabbit/tome-blocks-core@0.7.0

0.6.xMinor

• Editorial Spread refinement + new Editorial Section block.

  • editorialSpread: expand from one default variant to five — rail-left (default), rail-right, rail-top (horizontal running head), rail-both (dual marginalia: structural left / referential right), emphasis (no-rail statement band).
  • Living rail: auto-derived index from a consumer-passed ordinal (manual rail.index still overrides), opt-in rail.sticky, rail.links (mini-nav), rail.asides (footnotes/asides); the media field re-homes from the main column into the rail. kicker/index/caption/statCallouts unchanged. railSide deprecated (superseded by the variant; retained for back-compat).
  • .main is now a subgrid pass-through so nested blocks resolve their own breakoutWidth (reading column by default, breakout for media/grids) — no new width system.
  • New editorialSection block: a banded reading-column section with NO rail — the lighter sibling for prose that doesn't need marginalia (reserves the spread for content that earns a rail).
  • README: documents the variants, the living rail, the consumer ordinal contract, and the usage doctrine (when to use Editorial Spread vs Editorial Section vs a standalone block).

  Backward-compatible: existing editorialSpread documents render unchanged (un-migrated docs fall back to rail-left/railSide). Consumers re-curate the main allowlist and wire the ordinal prop.

• @wabbit/tome-blocks-core@0.5.9

0.5.xMinor

• Add editorialSpread (rail + config-injected nested-blocks main, banded, subgrid-native) and compareColumns (two-column compare).

  Both consume the canonical @wabbit/tome-ui named-line breakout helper.

0.4.x

0.3.xMinor

• Sprint 3 blocks split — v0.2.0

  Extracted the Tome blocks monolith (@wabbit/tome-blocks) into independently publishable bundle packages. Each bundle is independently installable, tree-shakeable, and testable in isolation.

  New packages (all v0.2.0):

  • @wabbit/tome-blocks-core — registries, defineBlock/defineBundle, variants, thumbnails, admin components (BlockPicker, VariantPicker)
  • @wabbit/tome-blocks-marketing-starter (free) — 8 marketing blocks: Hero, FeatureHero, CTA, LogoSlider, Pricing, Testimonial, FAQ, Banner
  • @wabbit/tome-blocks-content-writer (free) — 10 editorial blocks: Blog, Archive, PostHero, RelatedPosts, EditorialOpener, EditorialBridge, EditorialSidenote, EditorialFigure, EditorialColophon, EditorialFootnotes
  • @wabbit/tome-blocks-agency-essentials (starter) — 10 agency blocks: About, Contact/Form, Gallery, Media, SplitView, Stat, StatBar, TeamRoster, Timeline
  • @wabbit/tome-blocks-editorial-pack (pro) — 8 editorial blocks: DataHero, Feature, InfoPanel, MessagePanel, MetricStrip, SplitPanel, StatusBoard, TextReveal
  • @wabbit/tome-blocks-signal-theme (pro) — 33 Signal narrative blocks
  • @wabbit/tome-blocks-lms-pack (pro) — scaffold for LMS blocks (Wave 3)
  • @wabbit/tome-blocks-catalog-pack (pro) — scaffold for catalog/ecommerce blocks (Wave 3)
  • @wabbit/tome-blocks-sc-pack (niche) — scaffold for Star Citizen blocks (Wave 3)
  • @wabbit/tome-blocks-extras (pro) — 47 residual blocks (heroes, layout, content, marketing)

  @wabbit/tome-blocks is now a meta-package that re-exports all bundle packages and provides registerAll(blockRegistry, bundleRegistry) as a convenience function.

  Render colocation: All 113 render .tsx components migrated from the monolith into their owning bundle packages (./render subpath on each bundle).

  Breaking changes (internal):

  • @wabbit/tome-blocks/blocks and @wabbit/tome-blocks/bundles subpaths removed (were Sprint 2 shims)
  • packages/blocks/src/render/ category index files removed (replaced by per-bundle ./render subpaths)

  Migration:

  // Before (monolith singleton, all blocks loaded)
  import "@wabbit/tome-blocks";
  
  // After (explicit registration, tree-shakeable)
  import {
    blockRegistry,
    bundleRegistry,
  } from "@wabbit/tome-blocks-core/registry";
  import { register } from "@wabbit/tome-blocks-marketing-starter";
  register(blockRegistry, bundleRegistry);
  
  // Or use the meta-package convenience function
  import {
    blockRegistry,
    bundleRegistry,
    registerAll,
  } from "@wabbit/tome-blocks";
  registerAll(blockRegistry, bundleRegistry);

• Updated dependencies [f2202cd]

  • @wabbit/tome-blocks-core@0.3.0