Blocks Marketing Starter

0.49.xMinor

• Six new free blocks for a product home page and an about page (stop viewer, switch tally, proof ledger, terminal steps, layer stack, term rows) and a Command Close variant of the call to action.

  Additive: stored documents and the existing blocks and variants render the same markup. Each new block ships a demo and a gallery entry, and none needs a paid pack.

  • stop-viewer: a rail of stops beside one framed picture, with a site/admin toggle (hidden for a stop with no admin picture), a route bar, a description, a command or a note, and an open button. The picture links to the stop's page. Every stop is in the server HTML and the first is selected, so it reads and indexes without JavaScript; the rail and toggle are plain buttons with aria-pressed.
  • switch-tally: switches for add-ons with a running total and the exact install line, each package printed once. The currency, the period, the command prefix, every price and every label are fields; nothing is priced in code. The whole switch row is one 44px button with role="switch", and on narrow screens the total stays pinned above the switches.
  • proof-ledger: a heading, promises, a large figure with its caption held together and centered against a window that names each check, and a row of small figures. Every number is stored content.
  • terminal-steps: numbered steps beside a terminal pane whose lines are commands or output. Step bodies take rich text or plain text.
  • layer-stack: rows from the top of a system to its base, each with a label, a body and a tone (accent, neutral, optional with a dashed outline, base inverted).
  • term-rows: rows of a large term beside its reason, as a definition list.
  • cta command-close: an inverted closing band with the title at the left and, at the right, a lead, an optional command with a Copy button, a reassurance line, link buttons and a quieter line for a second audience. With no command set, the command area and the Copy button do not render. The new fields (closeTitle, closeLead, closeCommand, closeReassurance, closeDoor, copyLabel, copiedLabel) show only for this variant.

  All of it is painted from the page colors (the foreground and background swapped for dark bands, the primary color for the accent band), so it follows the site's palette. Motion respects reduced motion, and the bands show in full when scripting is off.

  The package now has three small client modules (StopViewer.client, SwitchTally.client, CopyCommand.client); the other new renderers are server components.

0.47.xMinor

• testimonial: consent-aware hiding, and an opt-in disclaimer line.

  A row from a testimonials collection (tome-local's local-testimonials, or any collection with a consent group) whose consent.given is false is no longer shown, in single, carousel and quotes-grid; the carousel's dots count only the rows that show, and a block with nothing left to show renders nothing. A row with no consent record, or one with no given yet, renders exactly as before, and so do inline entries (the existing golden holds the default markup byte for byte).

  The stored shape is unchanged.

  testimonialBlock.block({ disclaimerLine: true }) adds a localized disclaimer text field, printed once under the quotes as data-testimonial-disclaimer. Off (the default), the block's fields are identical; turning it on adds one column, so SQL sites need a migration at that point.

0.45.x

0.44.xMinor

• The banner can now be dismissed by the visitor, and the venue hero takes up to four actions and a photo credit.

  Everything is opt-in: a banner or hero you already have renders exactly as before.

  • Dismissible banner. Turn on "Visitors can dismiss it" and give the message a short key (for example closure-2026-11-02). A close button appears, and the visitor's choice is remembered in their own browser only, either for the visit, for 24 hours, or until you change the key. Nothing is sent to a server and no cookie is set. If the browser blocks storage the banner simply shows every time. Change the key and everyone sees the new message. New fields on the banner: dismissible, dismissKey, dismissMemory, dismissLabel and showUntil (after that time the banner no longer renders, even without the dismiss option). A dismissed banner is hidden before first paint by one small inline script; if your site sets a strict content-security policy, allow that script by hash or nonce (the script is a fixed string exported as BANNER_GUARD_SCRIPT from the banner's dismiss module), otherwise the banner hides a moment after load instead. With the option off there is no button, no script and no client code in the markup.
  • Venue hero: up to four actions. The venue variant of high-impact-hero now accepts four links instead of two. Every other variant stays at two, enforced on save; stored documents and their admin screens are unchanged.
  • Venue hero: photo credit. A new optional venue.mediaCredit text prints a credit on the photo as figcaption[data-hero-credit], after the image. It needs a photo, and only the venue variant shows it. When it is set, the photo wrapper is a figure instead of a div; without a credit the markup is unchanged. Themes can restyle the chip with --tome-hero-credit-ink and --tome-hero-credit-bg.

  New fields are nullable columns: on a SQL database, regenerate your migration. The banner now ships one small client file (BannerDismiss.client.tsx), loaded only when the banner is dismissible.

• The testimonial quotes-grid layout marks its first quote for themes.

  The first quote's <figure data-testimonial-cell> carries data-testimonial-lead, so a theme can set a lead quote. The stat tile never takes it, whatever its position.

  Other layouts and the other quotes render as before.

  The venue hero photo is the page's LCP image, so it now loads first.

  The venue variant's background photo is asked for with priority and fetchPriority="high" (eager, high fetch priority). It was loading="lazy" with no priority.

  A media adapter that renders next/image must forward fetchPriority itself (next/image 16 does not infer it from priority). Only venue changes; the other variants render as before, and the venue golden is unchanged because its stand-in adapter ignores the hint.

  The venue photo wrapper no longer depends on the engine to find its width.

  [data-hero-media] on the venue variant has a stretched height and an image with its own ratio, so WebKit (and every engine at 1024px) could work its width out from the row height and leave the photo narrow. The pack's stylesheet now states inline-size: 100% on the wrapper, so every theme gets a full-width photo without patching it.

  CSS only: where the width already resolved to 100% the layout is unchanged, and the markup (the venue golden) is identical.

0.43.x

0.42.x

0.39.xMinor

• faq can group its questions, set its closing callout beside them, and change the callout by the hour.

  Three optional fields, none with a default:

  • faqs[].group: files a question under a heading. Questions sharing a label are gathered under one <h3 data-faq-group-title> in a data-faq-group wrapper, in the order the labels first appear; questions with no label form a group of their own. With no group set the list stays flat.
  • calloutPlacement: 'aside': the callout becomes an <aside> card (data-faq-callout-placement="aside") beside the questions as a sticky card from 1024px, and stays under them on phones.
  • calloutTextOpen and calloutTextClosed: rich-text copies of the callout, marked data-when-open and data-when-closed beside a neutral data-when-neutral copy from calloutText. The block's stylesheet chooses by <html data-tome-open="true|false">, the attribute chrome writes from the site's hours; with it absent the neutral copy shows, so a site without hours never reads "closed". A side left empty falls back to calloutText.

  Stored documents that set none of the new fields render byte-identical markup (pinned by a golden test).

  Purely additive: no peer is added or tightened, no field has a default, and nothing changes for a site that sets none of them.

• faq can show a second link after its callout link.

  calloutSecondLink { label, url } (optional, no default) renders a quieter text link after the callout link, marked data-faq-callout-second, for a second destination such as "All parent questions". It shows only with both a label and a link, and a javascript:, data: or vbscript: link is ignored.

  The label is localized.

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

0.38.xMinor

• The split high-impact-hero can turn a supporting image's caption into a chip with an add-to-bag button, and show its proof line as separate facts.

  BREAKING: the @wabbit/tome-blocks-core peer range is now >=0.38.0 <1.0.0, because the chip renders through the new AddToBag adapter. Migration: upgrade @wabbit/tome-blocks-core to 0.38.0 or later.

  The new fields add database columns: run your Payload migration and regenerate types.

  New optional fields, shown for the split variant only and empty by default, so stored heroes render unchanged: supportingImages[].shopAction (product slug, href, variantSku, label) and proofLine.segments[]. With a shopAction the caption becomes figcaption[data-hero-caption-chip] holding the caption and a span[data-hero-caption-action] that wraps the AddToBag control (a plain link to href until a commerce layer registers the real one; the wrapper is empty when there is nothing to link to).

  Segments render as span[data-hero-proof-segment] in place of the proof line's text. The chip wraps the caption name in strong[data-hero-caption-name].

  A new optional split-only eyebrowLead text renders b[data-hero-eyebrow-lead] before the eyebrow ("Batch 14 · out of the kiln"); empty renders the eyebrow unchanged.

• The testimonial block's quotes-grid layout gains an opt-in portrait.

  The new checkbox showPortraits (shown for quotes-grid only, off by default) renders a quote's image as a round portrait, div[data-testimonial-portrait], at the start of its attribution, with the name and role beside it; a quote with an image and no name still gets a caption. The portrait is sized by --tome-testimonial-portrait-size.

  The images were already stored (entries[].image) but the grid never showed them, so with the option off, unset or false the grid, and every other layout, render exactly as before.

0.37.xMinor

• high-impact-hero split gains a media side, a proof line, a motif plate and theme hooks.

  mediaSide (start | end, empty reads as end) moves the supporting images before or after the copy. The proofLine group, which only quick-ask showed, is now also shown on split, as one line under the buttons.

  An optional motif (image, alt; alt text required when an image is set) renders as a small plate beside the proof line. split also writes neutral hooks for themes: data-hero-media-side, data-hero-copy, data-hero-subheadline, data-hero-media, data-hero-foot, data-hero-proof, data-hero-proof-lead and data-hero-motif.

  Every new field is optional with no default; the other variants render byte-identically, and a split block differs from before only by the added data attributes.

  testimonial gains an optional titleLevel (h2 | h3, used with the custom section title) and faq an optional calloutAfter text.

  • `testimonial` `titleLevel`: the custom section title renders as an h3 today. A block that opens its section with no heading above it can set titleLevel to h2 to emit an h2 instead. Empty, h3 and any other value render the h3 the block always rendered, byte for byte.
  • `faq` `calloutAfter`: a short line (for example "I read every one.") rendered after the callout link as <span data-faq-callout-after>, inside the callout. Empty or blank renders nothing and the markup is unchanged.
  • Payload migration: both are new optional fields (a select and a localized text), so Postgres sites that register these blocks should run payload migrate:create and payload migrate after upgrading.

0.36.x

0.35.xMinor

• BREAKING: these packs now need @wabbit/tome-blocks-core 0.35.0 or later, because they read the wrapper's new data-block-placement instead of its inline style text.

  Migration: upgrade @wabbit/tome-blocks-core to 0.35.0 or later alongside these packs. A site that renders its own block wrapper (with data-tome-block-wrapper) on a span other than 1 / -1 should add data-block-placement={blockPlacementFor(span)} to it; a wrapper without the attribute is read as full width.

  • @wabbit/tome-blocks-local-pack: in Safari, the price list's teaser list and the logistics block's content touched the viewport edges once the page had scrolled. Their side padding depended on matching the wrapper's style text, which WebKit rewrites as grid-column-start/grid-column-end longhands as soon as the scroll reveal writes to it. The padding rule now reads data-block-placement. Chromium and Firefox render as before.
  • @wabbit/tome-blocks-house: LaneGrid decides whether to subgrid its block wrapper (full row, content column, or its own tracks for any other span) from data-block-placement, so the decision no longer changes in Safari after the scroll reveal runs.
  • @wabbit/tome-blocks-marketing-starter: exhibit's nested block wrappers carry data-block-placement, matching RenderBlocks.

0.34.xMinor

• testimonial quotes-grid and faq gain the options a theme needs.

  • testimonial `quotes-grid`: new optional eyebrow, a small section label above the section title (<p data-block-eyebrow>); the block had no label field, so a "Client voice" label had nowhere to go. The grid's column count is the token --tome-testimonial-grid-cols (defaults unchanged: 1, 2 from 640px, 3 from 1024px). The stat value supports the *asterisk* accent convention: "9 _in_ 10" renders "in" as <em data-testimonial-stat-unit>, upright and smaller (--tome-testimonial-stat-unit-size, default 0.5em). A value with no stars renders as before.
  • faq: new calloutStyle (box by default, or line). line sets the closing "still have a question?" bridge as a plain start-aligned line with a text link and marks it data-faq-callout-style="line". The bridge and its link carry data-faq-callout and data-faq-callout-link, and the header group and badge carry data-block-header and data-block-eyebrow, so a theme can restyle the badge chip.
• Narrow-screen rules that never fired now fire.

  These blocks wrote their phone layout as an unnamed @container query, but nothing around them declares a size container (not tome-ui, the blocks core or the starter), so the rules never matched: the high-impact-hero split and default layouts never stacked on phones. Declaring the container on the block root would not work either, because size containment turns a subgrid root into a plain grid and drops the page-grid lines its children sit on.

  The rules are viewport queries now, at the same breakpoints; the blocks are full-bleed, so the viewport is their width.

  • @wabbit/tome-blocks-marketing-starter: high-impact-hero (two columns stack to one, large headline sizes step down, at 768px and below).
  • @wabbit/tome-blocks-extras: BlogHero, ChapterHero, CustomHero, ImageHero, LowImpactHero, MediumImpactHero, PageHero, StudyHero, TypographyHero (768px) and SectionHeader (640px).
  • @wabbit/tome-blocks-content-writer: PostHero (768px).
  • @wabbit/tome-blocks-agency-essentials: SplitView stacks at 768px.

  Above those widths nothing changes.

0.33.xMinor

• New venue variant for high-impact-hero and new reserve variant for contact, for places people visit.

  • `high-impact-hero` `venue`: the venue name set very large, with a meta line, one line and one action. The background photo sits either behind the copy, over a theme-set scrim (--tome-hero-scrim), or full width above it. It is chosen by the new optional venue.mediaPlacement field (behind, the default when empty, or above). Hooks: data-hero-media-placement, data-hero-scrim, data-hero-meta, data-hero-name and data-hero-line, plus the existing data-hero-media and data-hero-actions.
  • `contact` `reserve`: a dark booking band that links out to the venue's booking provider. It has a GET form for party, date and time (labels partyLabel, dateLabel and timeLabel, default "Party", "Date" and "Time"), built from an editor-written reserve.urlTemplate with {party}, {date} and {time} tokens, and works without JavaScript when each token is a whole query value. Under the form come labeled sample-time chips (sampleSlots[] and sampleSlotsLabel, never live availability), then an "Or:" row (lead-in altLabel, default "Or:") with a tel: call action and altActions[] (link, call, or order, which opens the ordering drawer). Every label is optional and localized; empty, it renders the English default. With no provider set, the form hides and the band leads with its actions; contact rows render as a facts row. eyebrow and callAction are now also shown for reserve.
  • New subpath `@wabbit/tome-blocks-agency-essentials/reserve`: the band's pure URL helpers, plus enhanceReserveBands(), an optional, framework-free client enhancement. It fills today's date, keeps the chips in step with the form, and fills templates the GET form cannot carry whole. The renderer stays a server component.

  All new fields are optional, variant-gated and have no default value, so existing content renders byte-identical.

0.32.xMinor

• New optional fields and theme hooks: an inline call link on the split hero, image labels, a quotes-grid testimonial layout, an open-first FAQ, and a stat-strip note.

  marketing-starter, `high-impact-hero`: the split variant now shows callAction (label, phone) and renders it as an inline tel: link after the buttons, for example "or call (555) 010-2030" (data-hero-call). An empty label reads "or call" after buttons and "Call" without them.

  In every variant that shows supporting images, supportingImages[] gains label, a short tag set over the image such as "Illustrative photo" (data-compliance-label), and captionMeta, a smaller second caption line (data-caption-meta). Every variant that renders actions marks its action row data-hero-actions (quick-ask already did): the row holding the buttons and the inline call on split, otherwise the button row itself.

  The attribute is the only markup change.

  marketing-starter, `testimonial`: each entry gains an optional complianceLabel, shown with its quote in every layout (data-compliance-label). The layout select adds quotes-grid: every testimonial becomes a short quote in a responsive grid, with an optional stat tile (value, text, label, position) placed at its 1-based cell among the quotes, default 2.

  Hooks: data-testimonial-layout="quotes-grid", data-testimonial-cell on every cell, data-testimonial-stat on the tile, data-testimonial-stat-value on its value.

  marketing-starter, `faq`: an openFirst checkbox (default off) renders the first question open and marks the root with data-faq-open-first. Every FAQ now carries part hooks: data-faq-item on each <details>, data-faq-question on its <summary>, and data-faq-answer on a new plain <div> around each answer (the answer's own element comes from your rich-text adapter, which accepts only a class name).

  proposal-pack, `proposal-stat-strip`: an optional note renders a source or compliance line under the figures (data-stat-note), with the same tokens as the stats. When the section header does not show, the root now carries data-stat-strip-headless; nothing renders in the header's place, so no gap is left above the figures.

  Every new field is optional, and the rendered markup is unchanged while they are empty; the additions to existing output are the FAQ part-hook attributes, the unstyled answer wrapper, the data-hero-actions attribute on hero action rows, and the data-stat-strip-headless attribute on stat strips that already had no header. The new fields add columns, so run your Payload migration and regenerate types.

  extras: the shared HeroLinkList accepts an optional containerData (extra data-* attributes for its row element). Omitted, the row renders exactly as before.

0.31.xMinor

• Groundwork v1.1 block fields for the quick-ask hero and the estimate contact band.

  `high-impact-hero` `quick-ask`: proofLine gains an optional proofLead text field, rendered as a <strong data-hero-proof-lead> before the proof text (for example "Next opening:"). Fixed: at phone widths the status dot could wrap onto its own line away from its text.

  The proof line is now inline flow, and the dot shares a no-wrap run (data-hero-proof-start) with its first phrase: the lead, or the first word of the text. The rest of the line wraps normally.

  With no lead and no dot, the markup is unchanged.

  `contact` `estimate`: two optional text fields. eyebrow is a small meta-voice kicker above the heading (data-contact-eyebrow).

  formNote is a short meta line beside the form card heading (data-contact-form-note). When it is set, the heading and note share a wrapping head row (data-contact-card-head).

  When both fields are empty, the output is unchanged.

• Payload-free ./meta entries now match what each pack registers, and @wabbit/tome-dispatch, @wabbit/tome-longform and @wabbit/tome-readout add a ./demo entry.

  ./demo (dispatch, longform, readout): the root barrel's demo props (getDemoProps, the per-block getters, DemoContext) on their own subpath, with no Payload import, so a client bundle such as a block gallery can use them without pulling in the block configs. Additive; the root barrel still exports them.

  These packages ship raw Payload Block configs rather than defineBlock descriptors, so they have no ./meta entry.

  ./meta (extras, signal-theme): new extrasDeprecatedBlockMeta and signalThemeDeprecatedBlockMeta lists describe the 16 deprecated blocks each pack still registers for stored content but no longer offers. extrasBlockMeta and signalThemeBlockMeta are unchanged: they still list only the offered blocks.

  The deprecated signal-theme blocks' metadata moved from inline defineBlock arguments into payload-free <block>.meta.ts files; the registered descriptors are unchanged.

  ./meta (extras, marketing-starter): six motion blocks (image-marquee, marquee, showcase, logo-slider, pricing-plans, testimonial) now declare requiredCapabilities: ['motion'] in their metadata. defineBlock already added it at registration, so the registered descriptors are unchanged, but the ./meta entries lacked it and a gallery reading them could not tell these blocks need a motion provider.

0.30.xMinor

• BREAKING: the high-impact-hero quick-ask call action now shows on phones only, unless the new callAction.showOnDesktop checkbox is ticked.

  Migration: to keep the call action on screens 768px and wider, tick Show on desktop on the hero's Call Action (or set callAction.showOnDesktop: true). Phones are unchanged: the call still leads the actions there.

  The call link carries data-hero-call-desktop="true|false" so a theme can tell the two apart.

0.29.xMinor

• High Impact Hero gains a quick-ask variant: text left, media right, with a one-question form, a tap-to-call action and a proof line.

  Additive: the three new groups are optional, carry no defaults and appear in the admin only when quick-ask is selected, so existing heroes render as before. Adding the fields to a Payload config adds their columns, so run your usual migration.

  • `quickAsk` (label, options[] of label + value, submitLabel, action, paramName). Renders a plain GET form with a visible label and a real <select>, so it works without JavaScript. The selected value is sent as ?<paramName>=<value> (default need) to the action, a URL or #anchor (default #contact); params already in the action are kept as hidden inputs.
  • `callAction` (label, phone). A tel: link. It is the first action on phones (below 768px) and follows the form on wider screens.
  • `proofLine` (text, showDot). One short line under the actions, with an optional status dot.
  • The job caption reuses supportingImages[].caption.
  • Theme hooks: data-block-variant="quick-ask", data-hero-actions, data-hero-call, data-hero-quick-ask, data-hero-proof, data-status-dot, data-hero-media, data-hero-caption. Every hero variant root now also carries data-block-variant.

0.28.x

0.27.xMinor

• The pricing and testimonial blocks work without collections of their own: by default their cards and testimonials are entered on the block.

  Pricing. The block used to relate to a product-cards collection, which a site that only installed this pack doesn't have, so Payload refused to start once the block was registered. With no productCardsCollection option, the block now has two card lists (subscriptionCards, projectCards) with the fields the cards render: title, description, tier, badge, price, frequency, a custom-quote switch, features, and button text and link.

  Passing productCardsCollection keeps the relationship fields (selectedSubscriptionCards, selectedProjectCards) exactly as before. The renderer reads either.

  Testimonial. The block used to relate to a testimonials collection, with the same startup failure on a site without one. With no testimonialsCollection option it now has an entries list (quote, name, role, company, image, date): single mode shows the first, carousel shows them all.

  Passing testimonialsCollection keeps the testimonial / testimonials relationships exactly as before.

  BREAKING: a site that used either block with its old default must now pass the collection to keep its schema and stored data: productCardsCollection: 'product-cards' for pricing, testimonialsCollection: 'testimonials' for testimonial.

• The pack works on a stock Next.js site: its per-block stylesheets now ship precompiled, so the site needs no next.config plugin.

  Each renderer's .tome-css stylesheet is compiled when the pack is built, into a JS module next to it (<Name>.tome-css.js / .cjs), and the renderers import that. A site no longer has to wrap next.config with withTomeBlockStyles to use the pack, and ./render and ./render/register now load under plain Node, so seed scripts, tests and the Payload CLI can import them.

  Each block's CSS is still inlined only on pages that render the block. A site that already uses withTomeBlockStyles needs no change.

  Scoped class names change once, because they are now keyed on the package rather than on where it is installed. The raw .tome-css files stay in the package as readable source.

0.24.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 10 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.
  • FeatureHero, HighImpactHero, LogoSlider, PricingPlans and Testimonial (client components) are now server-safe wrappers (X.tsx) around X.client.tsx; PricingPlanCard imports PricingPlans' stylesheet for class names. 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.

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 [090e984]

• Updated dependencies [73081e6]

  • @wabbit/tome-blocks-core@0.16.0
  • @wabbit/tome-blocks-extras@0.16.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

• cta: door-strip + doors variants graduated from tome-starter (showcase program Phase 3.7).

  Adds a doors array field (min/max 2 rows: voice, kicker, heading, body, link) and a columnSpan field to the base cta schema — both additive, backward-compatible. door-strip is a compact two-door router (whole-surface links, mono kicker, serif line, arrow affordance); doors is a full two-door close (kicker, serif heading, body, underlined go-link per door, scroll-reveal via the new @wabbit/tome-blocks-core Reveal helper — seed with columnSpan: '1 / -1' for full bleed).

  Both are style-only variants: the doors field lives on the base schema behind an admin.condition, not a fieldOverrides schema variant, because per-document schema divergence can't be expressed at config-build time (see comment in cta/variants.ts).

• exhibit: new gallery-wall block graduated from tome-starter (showcase Phase 3.7) — museum plates framing real nested block renders; nested allowlist via factory config (exhibitBlocks).

  Ports the starter's src/blocks/Exhibit/ (config.ts, Component.tsx, Component.module.css) into a new exhibit block: an asymmetric 12-col wall of hairline-framed white canvases, each holding a REAL nested block render (not a screenshot) under a plate caption (title + pack attribution). One style-only variant (gallery-wall), registered via plain defineBlock(meta, factory, variants) matching testimonialBlock's idiom.

  The nested blocks allowlist is a factory-config contract — pass config.exhibitBlocks (an array of Payload Block configs) when invoking exhibitBlock.block(config) to curate what's exhibitable; omitted, it defaults to this pack's own testimonial block so the field is never empty and the pack stays self-contained (no import of lms/catalog/org packs). The Exhibit render component takes an optional nestedComponents prop (registry-free resolution map for the nested per-exhibit blocks, checked before the shared @wabbit/tome-blocks-core render registry) and replicates RenderBlocks' per-block subgrid wrapper (data-tome-block-wrapper, data-block-background, gridColumn/gridTemplateColumns: subgrid) by hand around each RenderBlock call for DOM/CSS parity with the rest of the pack.

  Registered in both render paths: the legacy 'use client' side-effect barrel (./render) and the server-safe explicit registry (./render/register).

• Updated dependencies [f4d55c9]

• Updated dependencies [eb403d4]

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

0.11.x

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.xMinor

• Batch 1 (2026-06-27 inserter/variant architecture): author the usage/intent layer on the free high-impact-hero — it is the canonical free workhorse hero and the migration target for the deprecated low/medium-impact heroes.

  Additive metadata only.

  Deferred to the live-run pass (coupled with the instance data-migration + a visual A/B): the slug rename high-impact-hero → hero (with a back-compat alias) and the heroTextTheme parity field.

• Batch 2 feature consolidation (2026-06-27 inserter/variant architecture) — collapse the scattered feature blocks into the single featureHero.

  • Deprecated (still registered + rendered for back-compat, removed from the offered extras bundle + client-safe gallery meta): feature-masonry, feature-with-large-media, feature-with-three-steps, media-feature → the marketing-starter featureHero. Together with Batch 1's feature-hero-with-cards + feature-with-icon-grid, the whole feature family now consolidates to featureHero, whose 6-layout variant select already covers them all.
  • Authored usage/intent metadata on featureHero (now the sole offered feature block).
  • Deferred to the live-run reconciliation pass (brand-preserving but a field-semantics swap + data migration): featureHero's dual variant mechanism — make the 6 LAYOUTS the _variant (so the VariantPicker drives layout, not the unrelated 4-value style axis), move the style axis to a secondary field, and drop the inline variant. Instance migration (standalone feature blocks → featureHero + the right layout) is deferred to a later release.

  Tier note: the feature layouts consolidate onto the FREE featureHero (it already carried all 6 free); unlike heroes there is no distinct premium feature layout to gate, so there is no paid feature-pro.

  Ships in the linked family's 0.8.0 minor.

• Batch 4 — Marketing & Data (2026-06-27 inserter/variant architecture).

  These six blocks already ship as one-block-plus-4-variants (clean _variant, no scattered duplicates), so this batch is audit + usage-authoring, not consolidation.

  • Authored usage/intent metadata (Decision 4) on cta, logo-slider, pricing, testimonial, faq, banner — so assembling agents + the gallery/inserter can select, order, and configure them. Additive metadata only.
  • Audit finding flagged for the live-run reconciliation pass: pricing carries a slug-split (Payload block slug: 'pricingPlans' camel vs meta slug: 'pricing' kebab) AND a redundant inline displayOptions.variant ('full'|'compact') alongside the _variant axis. Documented in pricing/meta.ts; deferred (couples with the slug-split decision + a data migration). The other five are clean.

  Ships in the linked family's 0.8.0 minor.

• Updated dependencies [249b670]

• Updated dependencies [249b670]

• Updated dependencies [249b670]

• Updated dependencies [249b670]

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

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.x

0.5.xMinor

• high-impact-hero: add an illustrationHero variant (characterImage upload + characterPosition) for character-led heroes.

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
  • @wabbit/tome-blocks-extras@0.3.0