# Gritmind - Documents, Reports & Social ## One-pagers and proposals Build as HTML, print to PDF. A4 or US Letter, `18mm` margins. - Header: horizontal logo top-left at 22px tall, document type in mono uppercase top-right (`PROPOSAL`, `CASE STUDY`, `SOW`). In Word, use `assets/logo/gritmind-logo-full-navy-on-light.png` set to 22px (about 0.23in) tall - Title `36pt/1.1` weight 500, one accented word - Body `11pt/1.6` in `--body`, max `72ch` measure - never full-width text - Section headings `16pt` weight 600, with a mono uppercase kicker above in the accent - Numbers, dates, IDs, currency and code: **always mono** - Footer: page number in mono, `gritmind.com`, and the confidentiality line if the document carries one Tables: no vertical rules, no zebra striping. A `1px` hairline under the header row and between rows. Numeric columns right-aligned in mono, tabular figures on. ```css @page { size: A4; margin: 18mm; } @media print { a[href^="http"]::after { content: " (" attr(href) ")"; font-size: 9pt; color: #5c6475; } h2, h3 { break-after: avoid; } table, figure { break-inside: avoid; } } ``` Print styles are not optional - a proposal that breaks a table across two pages undercuts the argument that we are careful. ## Reports Same base, plus: - A contents page when it runs past 6 pages - Pull quotes at `20pt/1.35` weight 500 with a 2px accent rule above - Charts follow `deck.md` chart rules; render at 2× and place as images, or inline the SVG - An appendix in `9pt` for methodology and sources - cite the real source for every statistic; unsourced numbers are exactly the noise we claim to cut ## OG and social cards `1200×630`. Because they render as thumbnails, they must survive being small. - Ground `#fafafa`, or `#20243a` for case studies - Horizontal logo bottom-left at 27px tall - Headline in Alliance No.2 500 at `56–72px`, **max 9 words**, one accented word - Mono uppercase eyebrow above it with the accent dot - One geometric graphic element bleeding off the right edge at ~10% opacity - the radial tick dial or a resolved signal line. No photo, unless the card is about a team member (below) - Nothing in the outer 48px except the wordmark **Team photos** (decision `0001`). A post or card about a team member - a new hire, a team feature, a talk - uses a real, current photo of that person. Shoulders up, plain background or cut out, at least 800px on the short side (1200px preferred). Never stock, never an AI-generated or AI-edited face; background removal and colour correction are fine. Source photos stay in the shared drive, not in git. Generate them at build time from post frontmatter rather than by hand, so every post has one and none drift. ## Email Plain text or lightly styled HTML. No image-heavy templates, no tracking pixels, no "Sent from" banners. The signature is: name, role, `gritmind.com`. One accent element at most - usually nothing at all.