Apple-inspired brand guide for usable report and content production. This specimen shows how Apple-styled content handles assets, surfaces, type, tagging badges, notifications, data, recommendations, handoffs, and export checks.
Apple-styled content should feel calm, precise, generous, and product-like. Use whitespace and restraint first; use blue for action; use colour states sparingly and with enough contrast to survive PDF and print.
Use for covers, title pages, and calm executive documents. Keep clearspace generous and avoid nearby badges or dense controls.
Use only when the entire module is dark. The mark should feel intentional, not like a contrast workaround.
Use for small cards and preview tiles. Centre it optically and pair with one short label.
Use for co-branded pages. Keep both names aligned and let whitespace carry the relationship.
Primary canvas for reading. Use it for report pages, cards, and tables that need a premium quiet feel.
Use for subtle card grouping. The difference must be visible enough to explain structure.
Use for links, selection, chart focus, and the one action you want the reader to notice.
Use for headings and important facts. Softer greys are for metadata, not critical claims.
Use for pending verification or risk. Keep the hue warm and readable, not faint.
Use for verified wins. Pair with a label so the meaning survives grayscale.
AI visibility readiness
Large, confident, and simple. One idea per title.
What changed this week
Use section headings to answer what the reader is about to decide.
Use normal copy for explanation. Bold the decision. *Italicise nuance* or a non-blocking caveat.
Keep metadata small and quiet: source, date, owner, version. Do not let it compete with the main action.
Use quotes for direct feedback, reviewer notes, and cited source language. Keep them short and surrounded by whitespace.
Badges are inline metadata. They classify evidence beside a claim; they do not replace a notification or explain an action.
Evidence: Evidence:Verified Evidence:Partial Evidence:Inferred Evidence:Missing
Priority: Critical High Medium Low
| Badge | Purpose | Use example | Apple treatment |
|---|---|---|---|
| Evidence:Verified | Confirmed evidence | “Hero copy appears in first-fetch HTML” | Soft green chip with text label |
| Evidence:Partial | Incomplete support | “Two sources agree; one is stale” | Warm chip; never hides uncertainty |
| Evidence:Inferred | Judgement from pattern | “Likely entity drift” | Blue chip; keep caveat nearby |
| Evidence:Missing | Evidence absent | “No cited source found” | Red chip; do not use as decoration |
Purpose: block release until fixed. Use for privacy risk, missing required evidence, or broken export.
Example: “The public PDF includes a private source name. Remove it before sharing.”
Purpose: show risk that needs attention soon. Use for partial evidence or unresolved owner decisions.
Example: “Recommendation is ready, but the owner field is still empty.”
Purpose: explain scope or method. Use when context helps the reader trust the result.
Example: “This review covers A4, US Letter, and slide exports.”
Purpose: record a stable, verified pattern to preserve.
Example: “Light code blocks now match the page theme and remain readable.”
92%
Priority claims have evidence. Source: A001.
4
Message states tested. Source: A002.
12
Reusable report blocks covered. Source: A003.
0
Private artefacts in public export. Source: A004.
| Component | Purpose | Apple treatment | Example content |
|---|---|---|---|
| Cover | First impression | Large title, calm whitespace | “AI visibility readiness” |
| KPI | Executive metric | Rounded quiet card, one number | “92% priority evidence coverage” |
| Notification | Interruptive state | Soft colour, clear recovery action | “Remove private source name” |
| Brief | Delivery handoff | Light panel with concise fields | Task / files / acceptance / verify |
A001 — Token audit — High confidence; verifies surface, text, accent, and state roles.
A002 — Component review — High confidence; checks covers, cards, tables, badges, and alerts.
A003 — Export review — Medium confidence; confirms A4, US Letter, and slides outputs.
A004 — Redaction review — High confidence; confirms public-safe placeholders.
Use for a blocker that prevents the report from being trusted or read.
Owner: Design. Due: current iteration. Verify: the PDF no longer exposes private material.
Use for issues that reduce clarity but do not block interpretation.
Owner: Content. Due: next pass. Verify: owner and acceptance fields are present.
Use for a verified style pattern that should not regress.
Owner: Design. Verified: A004. Preserve: light code panels and readable state colours.
Task: Apply Apple-styled report components to an executive audit.
Files: report Markdown, brand renderer CSS, PDF exports.
Acceptance: every block has one purpose, clear label, accessible contrast, and print-safe layout.
Verification: render HTML, A4, US Letter, and slides; inspect badge, notification, table, and code readability.
Do: use fewer, clearer blocks.
Do not: use colour when hierarchy, wording, or spacing can solve the problem.Public artifact rule
Apple-styled public examples must not include private client names, URLs, local paths, screenshots, or raw exports.
Apple brand style guide specimen · usable production guide · public-safe placeholder content