Document Template Editor — Scope of editable fields

The current editor for the 4 system templates (Invoice / Sale Agreement / Odometer / Title Transfer) only exposes 3 raw HTML textareas. That doesn't match how the React renderers actually work — most of the document is structural, but some parts are real copy slots. What scope should the editor have?

Rich slot editor — well-defined editable zones with rich-text where it matters Recommended

Each template declares its editable zones in code. Editor surfaces ONLY those zones, with the right input type for each (single-line text, multi-line text, or rich-text editor for prose blocks). Structural items (header band layout, parties section, items table, payment block, footer chrome) are not editable because they're driven by data — that data comes from Company Profile, Order, and Listing.

Edit modal — Auction Invoice

Document Identity Editable

Shown in the band of the PDF — what this document is called.

Name (admin label)

Description (admin notes)

Title shown on PDF band

Subtitle (under title)

Header Band Identity System-managed

Logo, company name, address, registry numbers — driven by /admin/company-profile. Change them there.

🔒 Company: RepoMarket Holdings LLC · Miami, FL · FL-LLC-2024-007731

🔒 Logo: RH (placeholder — no upload yet)

Perks & Inclusions Box (green) Editable · Rich text

"What's included with your purchase" block on the invoice. Use bullet list.

6-Month / 10,000-Mile Limited Powertrain Warranty — covers engine, transmission, transfer case, drive axles
14-Day Return Policy — return shipping arranged and paid by RepoMarket
Free Delivery within 1,000 miles of pickup point
Title Documents issued by mail within 30 days of payment clearance

Terms strip (yellow, bottom) Editable · Rich text

Legal fine print at the bottom of the invoice page.

Subject to the Vehicle Sale Agreement and Terms of Service. See verify URL below to confirm document authenticity.

Document Structure System-managed

Parties section, line items, payment block, totals card — all driven by Order data + Payment Method. Cannot edit here.

🔒 Parties section (Issued by / Billed to) — from CompanyProfile + Order.billing*

🔒 Line items — from Order.totalAmount + Listing

🔒 Payment block — switches based on Order.paymentMethodType + Bank Account

Routing & Signatures Editable

Signer party

Require signature

Pros Each template has the right slots · rich-text editor (Tiptap) for prose · single-line inputs for titles · clear separation of "structural" vs "editable" · less room for admin to break PDFs · self-documenting via the system tags

Cons Each template needs a small registry entry declaring its slots · build cost ~1 day (Tiptap was already in deps per CLAUDE.md)

Option A + per-template logo / colors override

Same as A, but each template also gets its own optional logo upload and color overrides (band color, accent color). Falls back to Company Profile defaults when blank. Useful if you want, e.g., a different color for invoices vs contracts.

Edit modal — adds Visual Identity section

Visual Identity Editable

Optional overrides — leave blank to use Company Profile defaults.

Logo (this template only)

Band color override

... (everything else from option A) ...

Pros Future-proof if you want, e.g., burgundy band on Title Transfer vs orange on Invoice (it's already hard-coded that way — exposing it as an override matches reality)

Cons Adds 4-5 fields per template that are rarely changed · slippery slope toward making renderers "data-driven" which makes them harder to keep tight to mockups · maybe YAGNI

Keep raw HTML textareas, just upgrade to a real HTML editor

Keep the 3 textareas (Body HTML / Footer HTML / Terms HTML) but upgrade them to a code-style editor (Monaco / CodeMirror) with HTML syntax highlighting. No structural changes.

Same 3 textareas, but with syntax highlighting

Body HTML

<ul>

  <li><strong>6-Month Warranty</strong> — engine, transmission, drive axles</li>

  <li><strong>14-Day Return Policy</strong></li>

</ul>

Footer HTML

(empty)

Pros Smallest change · power users see what they're typing

Cons Still wrong abstraction — most of what's in the textareas is plain text, not HTML · admin still can't change "what's shown on the band" (because it's not in textareas at all) · doesn't address the original complaint