Back to Index / Strategy & Ideation / Internal Document Style Guide
Dynery  ·  Internal Style Guide  ·  v1.0  ·  May 2026

Dynery Internal Document Style Guide

The complete visual and structural standard for all Dynery internal documents. Every doc should feel like it belongs to the same system.

Version  1.0 Owner  Wale Martins, CEO Applied to  All internal HTML documents
Overview

What this style guide governs

Every internal document — sprint briefs, strategy docs, creator framework materials, loyalty architecture, investment memos — must use this system. Consistency across documents is not aesthetic preference; it signals that the team operates with the same discipline it asks of restaurant partners and creators.

The three non-negotiables
  • Every document uses the dark gradient hero header — no exceptions
  • Body font is always Libre Franklin. Headings always Playfair Display. Metadata always DM Mono
  • Callouts use exactly three semantic variants: teal (informational), gold (narrative/strategic), rust (risk/warning)
Typography

Three fonts. One system.

Dynery uses a fixed three-font stack. No other fonts are permitted in internal documents.

Playfair Display — headings, hero h1, pull quotes, card titles
The Future of Local Dining
Section heading, weight 700
Pull quote text, italic
Google Fonts: Playfair Display · Weights: 700, 900 · Italic: 400i, 700i
Libre Franklin — all body text, callouts, lists, table content, labels
Body text at 17px, weight 400. Dynery is the coordination, discovery, and transaction layer for real-world dining behavior in Seattle. Every document should read with this clarity.
Supporting text at 14px, muted color — used for metadata, card body text, table cell content.
Google Fonts: Libre Franklin · Weights: 300, 400, 500, 600, 700
DM Mono — breadcrumbs, section eyebrows, badges, footnotes, metadata
Dynery · Strategy & Ideation · May 2026
Section label · document category · date issued
Google Fonts: DM Mono · Weights: 300, 400, 500 · Italic: 300i

Type scale

ElementFontSize / weight / color
Hero h1Playfair Displayclamp(28px, 4.4vw, 54px) · 900 · #ffffff
Hero h1 accentPlayfair Display italicSame size · 700i · #3d9e8e (teal-light)
Hero subtitlePlayfair Display italic17px · 400i · rgba(245,240,232,.66)
Section h2Playfair Displayclamp(22px, 2.6vw, 34px) · 700 · #1a1310
Section h2 emPlayfair Display italicSame · 700i · #2a7c6f (teal)
Card / subsection h3Playfair Display20px · 700 · #1a1310
Body paragraphLibre Franklin16–17px · 400 · #1a1310 · lh 1.7
Intro / lead textLibre Franklin15px · 400 · #6b6259 · lh 1.82
Callout textLibre Franklin15px · 400 · #1a1310
Section eyebrow (.kk)DM Mono10px · 400 · .26em spacing · uppercase · teal/gold/rust
Hero breadcrumbDM Mono10px · 400 · .26em spacing · #e8b96a
Hero metadataDM Mono10px · 400 · .14em spacing · rgba(232,185,106,.7)
Badges / pillsDM Mono9px · 400 · .1em spacing · uppercase
FooterDM Mono10px · 400 · .1em spacing · rgba(245,240,232,.42)

Google Fonts import

https://fonts.googleapis.com/css2?family=Playfair+Display:ital,wght@0,700;0,900;1,400;1,700&family=Libre+Franklin:wght@300;400;500;600;700&family=DM+Mono:ital,wght@0,300;0,400;1,300&display=swap
Color

The Dynery palette

Six semantic colors plus a neutral stack. Never introduce colors outside this palette in internal documents.

Ink
#1a1310
Hero bg, headings, table headers, footer
Teal
#2a7c6f
Section labels, teal callout border, links, teal badges
Teal light
#3d9e8e
Hero h1 italic accent, toc hover
Gold
#c9923a
Gold callout border, gold eyebrow labels
Gold light
#e8b96a
Hero breadcrumb, hero metadata strong
Rust
#b84c2e
Rust callout border, risk labels, warning text
Paper
#ffffff
Card backgrounds, table cells, venue bodies
Cream
#f4f4f4
Page background, TOC background, phase footers
Border
#c8c4bc
All borders, dividers, checklist separators
Muted
#6b6259
Intro text, supporting copy, metadata
Blue
#185fa5
Thesis block border, discovery loop accent
Purple
#534AB7
Phase 1 accent (loyalty phases only)
Hero header

The standard document header

Every internal document opens with this hero. It is the single most important consistency signal in the system. Do not use any other header treatment.

PropertyValueNotes
Background#1a1310 (--ink)Solid dark base, not gradient
OverlayDual radial gradientTeal at 78% 20% (28% opacity) + Gold at 8% 85% (16% opacity)
Padding84px 56px 72pxGenerous — the hero must breathe
Breadcrumb (.hvol)DM Mono, 10px, .26em, gold-lightFORMAT: "Dynery · [Pillar] · [Doc type] · [Date]"
h1Playfair Display, 900, whiteAt least one word must be italic in teal-light (#3d9e8e)
Subtitle (.hero-sub)Playfair Display italic, 17px, 66% whiteOne sentence. Operational description only.
Metadata (.hero-meta)DM Mono, 10px, gold-light 70%Issued · Owner · Relates to
The teal accent word rule

Every hero h1 must have at least one word or phrase wrapped in <em> to render in teal-light italic. This is the single visual signature that makes Dynery documents immediately recognizable. Examples: "Market Readiness", "Believes", "coordination, discovery, and transaction".

Callout system

One system. Three variants.

All callout blocks use the same structural pattern — a left border strip with a colored background tint. Three semantic variants. Nothing else.

Teal — informational / insight / investor narrative

Use for: key insights, strategic conclusions, investor-facing narrative, positive forward statements. Border: #2a7c6f · Background: rgba(42,124,111,.06)

Gold — important direction / caveats / sequencing

Use for: important caveats, sequencing notes, strategic priorities, CEO direction. Border: #c9923a · Background: rgba(201,146,58,.07)

Rust — risk / warning / contingency / blocker

Use for: risks, warnings, downgrade paths, open blockers, unresolved decisions. Border: #b84c2e · Background: rgba(184,76,46,.06)

Callout CSS pattern

.cal-t { background: rgba(42,124,111,.06); border: 1px solid rgba(42,124,111,.22); border-left: 3px solid #2a7c6f; padding: 16px 20px; } .cal-g { background: rgba(201,146,58,.07); border: 1px solid rgba(201,146,58,.25); border-left: 3px solid #c9923a; padding: 16px 20px; } .cal-r { background: rgba(184,76,46,.06); border: 1px solid rgba(184,76,46,.22); border-left: 3px solid #b84c2e; padding: 16px 20px; } .cal-label { font-family: 'DM Mono'; font-size: 9px; letter-spacing: .18em; text-transform: uppercase; margin-bottom: 7px; }
Do
  • One callout variant per semantic purpose
  • Always include a .cal-label above the content
  • Use lists inside callouts for multiple items
  • Keep callout text concise — this is emphasis, not body
  • Put the dark box (.dark) only for sprint themes / primary directives
Don't
  • Don't invent new callout colors (sage, blue, pink, etc.)
  • Don't use filled rounded cards as callouts — that was the old system
  • Don't use rust callouts for neutral information
  • Don't stack multiple callouts of the same color consecutively
  • Don't put an entire section inside a callout
Components

Standard document components

These are the building blocks available to every internal document. Use them as specified — do not modify color, font, or structural logic.

Checklist

Open list with teal dot markers and hairline row dividers. No container box. No background color.

Disposition badges

DM Mono, 9px, uppercase. Four semantic variants. Border-style only — no filled backgrounds.

In sprint Partial scope Deferred Operational

Pull quote

Every feature, integration, creator activation, map surface, and restaurant workflow must support the ecosystem outcome. If it doesn't strengthen one of the four loops, it waits. Wale Martins, CEO · Sprint directive

Dark box

Reserved for sprint themes and primary CEO directives only. Do not use for general content.

Sprint theme · May 15 to June 15

Ship Dynery Pay. Make it work for the World Cup.

Stability fixes that do not support this deadline are deprioritized. Investor proof comes from live transactions — not a polished dashboard alone.

Section eyebrow (.kk)

DM Mono, 10px, .26em letter-spacing, uppercase. Always placed directly above h2. Three color variants: TEAL (default) · GOLD (narrative) · RUST (risk)

Rules

What every document must include

Required in every document
  • Dark gradient hero with DM Mono breadcrumb, Playfair h1 with em accent, italic subtitle, metadata row
  • Sticky TOC navigation (except one-pagers)
  • Google Fonts import — all three fonts
  • Dark footer bar with document path and date
  • All body text in Libre Franklin — never Spectral, DM Sans, Instrument Serif, or any other font
Never permitted
  • Fonts outside the three-font stack (Spectral, DM Sans, Instrument Serif, System UI, etc.)
  • Callout colors outside teal / gold / rust
  • Filled rounded cards as callout treatments (the pre-May 2026 system)
  • Page backgrounds other than #f4f4f4 (--bg/--cream)
  • Hero headers other than the dark gradient standard
  • Inline styles that override type scale or color palette

Document naming & numbering

TypeLocationNaming pattern
DoctrineStrategy & Ideationdynery-[topic]-doctrine.html · Doc 32+
Operational SummaryStrategy & Ideationdynery-[topic]-ops.html · Doc 30+
PrinciplesStrategy & Ideationdynery-[topic]-principles.html · Doc 31+
Sprint BriefStrategy & Ideationdynery-sprint-brief.html
StrategyPillar → Strategydynery-[topic]-strategy.html
Style GuideStrategy & Ideationdynery-style-guide.html · This document
Template

Starter HTML template

Copy this skeleton for every new internal document. Replace placeholder text. Do not change structural CSS.

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Dynery — [Document Title]</title> <link href="https://fonts.googleapis.com/css2?family=Playfair+Display:ital, wght@0,700;0,900;1,400;1,700&family=Libre+Franklin:wght@300;400;500;600;700 &family=DM+Mono:ital,wght@0,300;0,400;1,300&display=swap" rel="stylesheet"> <style> /* [paste full shared CSS here — see any existing doc] */ </style> </head> <body> <div class="bc-bar"> <a class="bc-back" href="/">← Back to Index</a> <span class="bc-sep">/</span> <span class="bc-crumb">[Pillar]</span> <span class="bc-sep">/</span> <span class="bc-crumb active">[Document Title]</span> </div> <div class="hero"> <div class="hvol">Dynery · [Pillar] · [Doc Type] · [Month Year]</div> <h1>[Title with <em>italic accent</em>]</h1> <p class="hero-sub">[One sentence operational description.]</p> <div class="hero-meta"> <span>Issued [Date]</span> <span>Owner <strong>[Name, Title]</strong></span> </div> </div> <nav class="toc"> <a href="#section1">Section 1</a> <a href="#section2">Section 2</a> </nav> <section id="section1"> <div class="w"> <div class="kk">Section label</div> <h2>Heading with <em>accent</em></h2> <p class="intro">Lead paragraph...</p> </div> </section> <div class="doc-footer"> <span>Dynery Internal · [Pillar] · [Document Title]</span> <span>[Month Year]</span> </div> </body> </html>