Blocks Dossier Pack

• A "receipts" or "proof" section presenting several short case results side by side
• A portfolio strip where each entry needs a headline stat plus a one-line context brief
• A closing row that should end on a call-to-action tile rather than a plain link

• landing
• about
• marketing
• portfolio

Author 2-5 tiles: a case number, a proof value, an optional brief, and a subject. Toggle Tile Images on to add a header image per tile — untouched tiles render a bracketed placeholder. Pick a Variant: default (receipts band), field-manual (tighter document register), or filmstrip (full-bleed photographic strip, requires Tile Images on). Set a CTA Panel heading to close the row with a call-to-action tile instead of a plain link.

• evidence-sheet
• exhibit-artifact
• proof-plates

• You need a single full-bleed case study, not a row of short ones — use exhibit-artifact instead
• The entries carry no comparable numeral/stat — use a plain card grid instead

marketing-landing

• A receipts/results row that needs plain, unstyled outbound links rather than relationship-driven cards
• A "the record" band closing a case-study or evidence section
• A moment that wants exactly one result visually set apart from its peers

• landing
• about
• marketing
• editorial-article

Write a kicker and heading (wrap a phrase in *asterisks* for an accent run). Add up to 6 cells: kicker, stat, line, name, and an optional plain href + link label. Flag exactly one cell to invert it to a light card. Close with a see-all label + URL.

• case-file-grid
• evidence-sheet
• receipts-trio

• Each entry needs a real relationship-driven link with a resolved reference — use case-file-grid or proof-plates instead
• You need more than 6 entries — split into multiple rows or use case-file-grid

marketing-landing

• A project/engagement masthead summarizing client, scope, timeline, result
• A compact spec sheet before or after a case study
• A verticalized "at a glance" ledger paired with a short narrative opener

• landing
• about
• marketing
• dossier

Fill in Spec Rows (label + value, optional note, optional emphasis). Add Scope/Stack chips as needed. Pick a Treatment: Table for the default wide spread, Grid for a 3-column reflow, Strip for one compact glance row, or Ledger for a tall narrow column — Ledger unlocks the optional Opening Narrative field group beside it.

• case-file-grid
• exhibit-artifact
• proof-plates

• You need a single narrative paragraph with no label/value structure — use a plain content block

marketing-landing

• A data-backed argument that needs real, citable numbers
• A moment that wants to land a two-part statement with a visual ink-fill reveal

• landing
• about
• marketing
• editorial-article

Add up to 3 stats (numeral + value + label; flag the source cell as Muted). Write a body paragraph and, if citing external data, add Sources (label + URL — each renders as a real link). Fill the Ink-in pull with two runs: the first inks in the body ink color, the second in the accent color.

• case-file-row
• evidence-sheet
• proof-plates

• The numbers are not real/citable — use a plain statement block instead

marketing-landing

• A case study with no real photograph to show, but a real communication/document to reproduce
• A moment that benefits from a letter, memo, or transcript-style artifact

• dossier
• about
• landing

Set a Tag (the chip label). Add Header Lines (label/value rows), a Subject Line, a rich-text Body, and a Signature. Add a Caption to describe the artifact below it, and an optional CTA link.

• evidence-sheet
• case-file-grid
• proof-plates

• A real photograph exists for this moment — use a media block instead

marketing-landing

• Comparing 2-4 concrete deployments, tiers, or outcomes side by side
• A chooser section where each option needs its own floating card
• A closing proof row that wants one option visually flagged as the default/flagship

• landing
• pricing
• marketing

Write a kick label, heading (wrap a phrase in *accent*), and intro. Add 2-4 plates: kicker, title, body (supports **bold** and *em* runs), an optional stats line, and an optional inline link. Flag one plate for emphasis. Choose a Shell, or leave Auto to let the kicker-presence heuristic decide. Add a proof-capture image per plate where a real screenshot exists.

• evidence-sheet
• case-file-grid
• exhibit-artifact

• You have more than 4 comparable items — use a table or a card grid instead

marketing-landing

• A section arguing for transparency — "here is what actually happened," wins and losses both
• A quote-grid closing a methodology or process section

• landing
• about
• marketing

Write a kicker and heading (wrap a phrase in *asterisks* for an accent run). Write the body paragraph making the honesty case. Add up to 3 quotes — keep any non-flattering one if the source material includes it; the point of this block is not to only show wins.

• case-file-row
• evidence-plate

• Every quote is a straightforward win — a simple testimonial block is a lighter fit

marketing-landing

• A social-proof close listing client/partner logos alongside a short ledger of facts
• A "the numbers" section that wants a real logo wall, not a generic grid

• landing
• about
• marketing

Write a kicker. Add ledger rows (index, value, description) — keep numbering real and complete. Add up to 10 logos; the grid sizes itself to however many you add. Add a coda for a short centered closing line.

• case-file-grid
• proof-plates

• You have no real logos to show — an invented or placeholder-only grid is not appropriate here

marketing-landing

• Contrasting the old way against the new way (or a competitor against your own approach) as a single honest display
• A "before you decide" section that shows what changes across 2-3 options, row by row
• Closing an argument with a visual verdict rather than a paragraph of prose

• landing
• marketing
• dossier

Add 2-3 `columns`, each with a label, a display value, and an "emphasis" flag on the one option that should render in full ink (the rest render struck through, muted). Add up to 6 `rows`, each with one cell per column in column order. Optionally close with an anchored `closeText` statement. For an N-column feature matrix with per-cell Yes/No/tone values, use `comparison-table` instead — this block is for a short, opinionated 2-3-way contrast, not an exhaustive feature grid.

• comparison-table
• cost-ledger
• term-ledger

• You need more than 3 columns, or a feature-by-feature grid with many rows — use `comparison-table`
• The comparison is really just one product's price against nothing — use `price-table` instead

dossier

• "Which one do I need?" pages comparing 3+ options across many capabilities in a single scan
• A specification sheet where every option needs the same set of attributes checked off
• A feature matrix accompanying a pricing or plan page, distinct from the tiers themselves

• pricing
• landing
• marketing
• docs

Add a headline (required) and optional eyebrow/description. Add 2-6 `columns`, each with a label and an optional highlight flag for the recommended option. Add 1-24 `rows`, each with a label and a `cells` array — cell order follows column order; a missing cell renders blank rather than shifting the table. Give a cell a `tone` of "affirm" (accent, bold) or "absent" (muted) to make a column read as a shape at a glance. For a short 2-3-way opinionated contrast rather than an exhaustive grid, use `compare-ledger` instead.

• price-table
• compare-ledger
• term-ledger

• You are comparing exactly 2-3 options with a handful of contrast points, not an exhaustive feature grid — use `compare-ledger`
• There is only one offer with one price — a plain `price-table` or product CTA is enough

dossier

• Listing what changes, what is included, or what a term means, one row per item, with room for a paragraph of explanation per row
• A "how it works" or "under the hood" section that reads better as short labeled rows than as a table
• Pairing a small number of terms with a supporting photo or diagram beside the list

• landing
• marketing
• docs

Set the variant: `shifts` for a light band with a bold display term (the default, everyday case), `spec` for a dark, technical-feeling band with a mono accent term. Add an optional kicker, a heading (`*accent*` runs render italic accent), and intro rich text. Add `rows` — each needs a term and rich-text body. Optionally add a supporting figure (image + a placeholder note for when no image is set yet) that renders beside the rows. Close with an optional anchored statement (`**strong**`/`*em*` runs supported). For a strict 4-column forensic ledger (line/category/cost/what-compounds) use `cost-ledger` instead; for a feature matrix use `comparison-table`.

• cost-ledger
• comparison-table
• compare-ledger

• The content is fundamentally tabular with many columns — use `comparison-table`
• Each row needs a fixed line/category/cost/compounds shape — use `cost-ledger`

dossier

• Making the cost of inaction or a status quo concrete, one line item at a time
• A "here is what this actually costs you" section building toward a single closing statement
• Highlighting one specific cost line as the fact the reader cannot unsee

• landing
• marketing
• dossier

Add an optional kicker, heading (`*accent*` runs render italic accent), and intro paragraph. Set the three column-strip labels (line/category, the debit, what compounds). Add up to 6 `rows`: line (e.g. "L01"), category, the debit in plain language, what compounds, and a "lit" flag — mark exactly one row lit to render it as the dark plate the reader cannot unsee. Close with a codaKicker + codaText naming the total. For a strict term/definition ledger without the lit-row device, use `term-ledger`; for a multi-option comparison, use `compare-ledger` or `comparison-table`.

• term-ledger
• compare-ledger
• comparison-table

• You need more than 6 rows or a general feature matrix — use `comparison-table`
• There is no single "cost" narrative — a plain `term-ledger` fits a neutral list of terms better

dossier

• Breaking down the hidden or compounding cost of a decision, delay, or status quo into discrete line items
• A "here is what this actually costs" section that needs to read as itemized and audited rather than a single claim
• Closing an argument with one line-item table plus a single summary verdict on an inset band

• landing
• marketing
• about
• dossier

Author 2-10 `rows`, each with a line id, category, cost (debit) string, and an optional "what compounds" note; mark at most one row `emphasis` to accent it (typically a running total). Column header labels are editable and default to LINE / CATEGORY / THE COST (DEBIT) / WHAT COMPOUNDS. Add an optional `closingNote` for a summary verdict rendered on a dark inset band beneath the table, with its own `closingLabel` kicker. Use `compact` when the ledger sits inside a denser section and does not need the top strip.

• shift-rows
• fit-list
• grants-ledger

• fit-list

• There are fewer than 2 comparable line items — a single stat or a short paragraph makes the point faster
• The cost is a single number rather than several compounding factors — use a stat block instead

dossier

• Comparing 3+ plans, tiers, or offers feature-by-feature in a real table, not a card grid
• One column needs to read as categorically different from the others (e.g. an enterprise/agency tier reached by conversation, not checkout)
• A single column should be called out as recommended without going all the way to a fully inverted band

• pricing
• landing
• marketing

Author `columns` (one per plan) and `rows` (one per feature); each row's `cells` are positional against `columns` — `cells[i]` belongs to `columns[i]`. Set `zone2: true` on at most one or two columns for the full dark/accent inversion; set `highlightedColumnIndex` to a 0-based column index for a lighter featured tint on a different column. Set `conv: true` on a cell whose value should read as a conversational/mono-accent exception (e.g. "Conversation") rather than a plain value.

• price-table
• ledger
• fit-list

• fit-list

• There are only 1-2 columns to compare — a simple two-column split reads faster than a table
• Every column is equivalent with no tier needing special emphasis — a plain comparison table without the zone/highlight fields is simpler

dossier

• Every item already reads as "X becomes Y" — a timeline compressing, a cost dropping, a process simplifying
• A "here is what changes when you work with us" section built from 3-4 concrete transformations
• Reinforcing a single argument with a repeated visual rhythm (label / before / arrow / after) rather than a paragraph per point

• landing
• marketing
• about

Author 2-6 `rows`; each needs a label, a before headline, and an after headline (body copy and a thumbnail are optional). When any row sets a thumbnail, the thumbnail column activates for every row — rows without one render a blank placeholder frame. Use the shared Image Display controls to set the thumbnail fit/border/alignment. Keep rows to the 3-4 sweet spot; more than that dilutes the rhythm.

• ledger
• fit-list
• grants-ledger

• fit-list

• The benefits are not naturally before/after pairs — a plain feature list or `stat-bar` fits better
• There is only one transformation to show — a single stat or a short paragraph makes the point without the row apparatus

dossier

• Helping a visitor self-select in or out before they contact sales
• Building trust by naming who the offer is NOT for, alongside who it is
• Closing a pitch section with an honest qualifier rather than another benefit claim

• landing
• marketing
• pricing

Author up to 6 `buildItems` and up to 6 `skipItems` (short, single-line conditions each). Add an optional `kicker` + `heading` above the columns and an optional `closeText` anchored statement below — both accept `*em*` runs for an accented span. Keep each item to one line; this block is a scanning aid, not a place for paragraphs.

• ledger
• shift-rows
• grants-ledger

• ledger

• The offer has no real disqualifying cases — a forced "skip" list reads as false modesty
• The comparison needs more than two columns or per-item detail — use `grants-ledger` instead

dossier

• A sales or landing page section that pre-qualifies the reader before the pitch continues
• An offer page that wants to repel the wrong buyer as deliberately as it attracts the right one
• A closing statement (guarantee, refund line, commitment) that needs to sit directly beneath a fit judgment rather than float alone

• landing
• marketing
• about

Author an optional kicker + heading (wrap a phrase in *asterisks* for the accent run), then a not-fit label/body and a fit label/body — both plain prose paragraphs. The optional anchored close renders as one statement beneath a rule (also accepts *asterisk* accents). Any missing piece collapses cleanly: the block renders nothing when heading, both bodies, and the close are all empty.

• spec-sheet
• spec-plate
• zone-directory

• The comparison is a checklist of features rather than a spoken paragraph — a bulleted compare block fits better
• There is no honest "not for you" case to state — a one-sided pitch does not need this device

marketing-landing

• A page that offers the reader 2-4 distinct next steps or paths and needs each one named and justified before the link
• A "how you work with us" section splitting self-serve vs. guided engagement
• A landing page moment that wants the decision itself to read as the page's own design device

• landing
• marketing
• about

Author an optional eyebrow + heading (wrap a phrase in *asterisks* for the accent run) + description, then 2-4 cells: each takes a number (renders as an outline numeral), a kicker, a title, a description, a go label (type the arrow glyph yourself — the component does not add one), an href, and an optional dark toggle to invert that one cell's register. The board's column count and border layout adapt automatically to however many cells (2, 3, or 4) are authored.

• fit-prose
• spec-sheet
• spec-plate

• There is only one path forward — a single CTA needs no directory
• More than 4 destinations are being compared — this reads as a considered decision, not a menu; use a larger grid block instead

marketing-landing

• Stating the concrete terms of a paid engagement, sprint, or audit directly on the page (duration, price, next step)
• A proposal or process page that needs a scannable terms strip near a CTA
• Any place a handful of short facts belong side by side, not in prose

• landing
• marketing
• about

Author 1-4 cells, each an optional label + value pair; the strip's column count matches however many cells actually have content, so the row fills edge to edge without a phantom empty column. Add an optional note for a single muted qualifying line beneath the row. The block renders nothing if every cell is empty and no note is set.

• spec-plate
• fit-prose
• zone-directory

• There are more than 4 terms to state, or the values need explanation — use `spec-plate`'s larger grid with its heading + lede instead
• The content is really prose, not discrete label/value facts

dossier

• Listing the technical stack or specs behind a build for a reader who asks, without making it the pitch
• A "Under the Hood" or "Tech Specs" section on a platform, product, or case-study page
• Launch-detail lists (ownership terms, what's included) that read as facts, not marketing copy

• landing
• marketing
• about

Author an optional heading (wrap a phrase in *asterisks* for the accent run; `headingFace: display` renders it at the larger elevation-page serif size) and lede, then up to 6 cells: each takes a label, a value, and an optional small note line beneath the value. Use `spec-sheet` instead when there is no heading/lede and 4 or fewer plain terms to state — the two blocks are intentionally not merged; this one carries a head and a larger cell cap.

• spec-sheet
• fit-prose
• zone-directory

• There is no heading or lede to frame the cells — `spec-sheet` is the leaner fit
• More than 6 facts need stating — split into two plates rather than cramming the grid

dossier

• A retrospective or "we tried this, and here is what happened" disclosure section
• A sequence of attempt/outcome/lesson entries that reads like lab notes or a changelog narrative
• A closing handoff that sends the reader to a follow-up resource or a next step

• editorial-article
• about
• docs

Author a headline and 2-8 entries (kicker + body; mark one as emphasis for the accent landing). Add an optional italic subtitle under the headline, and an optional closing handoff (label + body + link). Toggle the top strip off via "Show Section Header" without losing its text — useful when this block follows another one closely. Switch spacing to "Spacious" for an airier, larger-type treatment.

• phase-ledger
• practice-modes
• wall-rows

• The content is a forward-looking roadmap rather than a retrospective — use `phase-ledger` instead
• There is only one point to make — a single paragraph beats the notebook conceit

dossier

• A course or program page listing its phases/modules in order, each with a scope and an outcome
• A step-by-step process or roadmap where each step needs more than a one-line label
• Proving a curriculum is real and complete — the register gate is exactly this: no gaps, no out-of-order phases

• docs
• about
• editorial-article

Author 1-9 phases in strict order, each with a number, an optional chip tag, a title, a body paragraph, and an optional italic outcome line. `*accent*` runs in the heading render as the band-relative accent-italic style. Keep the phase count real — gaps or reordering break the register the block is built to prove.

• lab-notes
• practice-modes
• wall-rows

• There are fewer than 2-3 real steps — a single paragraph or a `stat-bar` communicates it faster
• The steps are interchangeable/parallel rather than sequential — a card grid fits better than a numbered ledger

dossier

• Explaining that the same practice/method has exactly two usable modes and describing each
• A "how people actually use this" section that needs two contrasting descriptions, not a feature list
• A closing statement that anchors the section with an optional pointer to more detail

• editorial-article
• docs
• about

Author exactly two modes (label + body each). Add an optional kicker and heading above them (`*em*` runs render serif-italic accent). Close with an anchored statement (`*em*` runs render the same way) and, optionally, a real link — leave both close-link fields blank if the beat has no follow-up.

• lab-notes
• phase-ledger
• wall-rows

• There are more than two modes/variants to compare — a card grid or table fits better
• The two things being compared are not equal in weight — an asymmetric layout communicates that better than two even columns

dossier

• Listing a set of asks/requests and the same verdict landing on each one, to make a pattern visible
• A "we said no to this, repeatedly" section where the repetition of the verdict word IS the point
• A closing statement that needs a bordered, scannable ledger of examples behind it

• editorial-article
• about
• docs

Author a kick label, a heading (`*accent*` runs render serif-italic accent), and an intro rich-text paragraph. Add any number of wall rows — each with a required "who," an optional "need" body, and an optional verdict word rendered bold and large at the row end. Close with an anchored statement; `**strong**` runs render semibold.

• lab-notes
• phase-ledger
• practice-modes

• Every row has a different verdict — the block's whole point is ONE repeated verdict word; use a table instead if verdicts vary
• There is only one example — a single pull quote communicates it with less furniture

dossier