A · Live editor look (reference)
Live capture not available this run (no browser MCP). Existing walkthrough + design-system screens. Full notes: ref-screens/README.md in the project folder.
PDT-308 · Microsoft Q4. Smart single Allow for tenant; partner Apply your brand colors + Undo + first-use auto-apply (Oct 12). Email + LP + custom docs as one flow. Lock / include-locked / per-row buried. FORM tokens.
Hero fill is painted (light blue) → smart Allow on → maps to accent.
Painted brand band → primary.
Neutral advisor strip — Allow off by default.
Body copy (near-black, unpainted) — Allow off. Privacy-looking links stay unless tenant opts in.
Landing page hero. Fill → accent/primary by tenant role.
Dark band → primary.
Neutral gray — smart default Allow off. Stays put.
Custom document body. Same color-apply rules as email/LP. Richer font surface (see E).
Section fill maps to primary (or accent via role).
Hero fill is painted (light blue) → smart Allow on → maps to accent.
Painted brand band → primary.
Neutral advisor strip — Allow off by default.
Body copy (near-black, unpainted) — Allow off. Privacy-looking links stay unless tenant opts in.
Hero fill is painted (light blue) → smart Allow on → maps to accent.
Painted brand band → primary.
Neutral advisor strip — Allow off by default.
Body copy (near-black, unpainted) — Allow off. Privacy-looking links stay unless tenant opts in.
We’ll remember this for emails, landing pages, and custom documents. You can still Undo on any asset. Change later in profile (placement TBD).
Hero fill is painted (light blue) → smart Allow on → maps to accent.
Painted brand band → primary.
Neutral advisor strip — Allow off by default.
Body copy (near-black, unpainted) — Allow off. Privacy-looking links stay unless tenant opts in.
Hero fill is painted (light blue) → smart Allow on → maps to accent.
Painted brand band → primary.
Neutral advisor strip — Allow off by default.
Body copy (near-black, unpainted) — Allow off. Privacy-looking links stay unless tenant opts in.
Tenant settings · Proposed IA split. Portal chrome stays as today; Content branding is the new named-role kit for email / LP / custom docs templates.
Partner portal chrome: primary colors, fonts, buttons. Does not drive email/LP templates.
Named roles for templates. Tenant paints with a role; account kit maps by name — no hex tagging.
Tenant defines roles once. Templates bind to roles. Account Brand Kit (Account Intelligence) supplies values per account. Join is on the name.
| Role | Maps to account kit | Used on |
|---|---|---|
| Primary | colors.primary | Section fills (default), strong bands |
| Secondary / Accent | colors.accent | Hero fills, two-tone |
| Text | textPrimary | Painted headlines |
| Link | link | Painted links only |
| Button | buttonPrimary | CTA fill + text |
| Heading / Body font | typography.fontFamilies | LP + custom docs; email TBD |
Show the UX idea even if V1 is unclear. Anjani Sep 23: email = Google Fonts list only; LP + custom docs apply brand font when kit is on. Ben Oct 12: fonts may be in V1. PDT-256 tenant upload is parking lot / cut for Q4 capacity.
Partner picks within the allowed list when kit applies. No custom file upload in email. If kit family missing → closest match or skip (open).
Apply heading/body family from kit when Allow is on. Keep template weight & role. Asian translations need Arial-type fallback + system message.
Same as LP if family is in catalog. Licensed custom fonts need PDT-256 (tenant) or partner upload — not in color V1 story.
Live capture not available this run (no browser MCP). Existing walkthrough + design-system screens. Full notes: ref-screens/README.md in the project folder.