Summary
- Use monospace as a role for concise interface text—navigation, section labels, dates, tags, and code—rather than setting long-form prose in it. Brittany Chiang’s archived v4 portfolio is a clear coder-oriented example: navigation, overlines and subtitles, experience tabs and date ranges, and code use a mono stack; its body and post paragraphs stay in a sans stack with 1.3–1.5 line-height. The font tokens make the pairing explicit: sans for reading, mono for technical/UI accents. The current portfolio says it uses Inter throughout, so treat v4 as an archived design precedent, not current styling.
- A useful counterpoint is Julia Evans’s blog: its first-party stylesheet uses PT Serif for body prose, a sans face for navigation and metadata, and monospace for code. The transferable principle is the division of labor: preserve a comfortable proportional face for paragraphs, and reserve mono for short technical or structural cues.
- The IBM Developer typography guide makes a similar role distinction: Plex Mono carries expressive headlines, code, and data points, while Plex Sans handles informative/supporting copy. It is a brand-system reference rather than a personal-site example.
Inline PDF pattern
- Gwern.net’s stylesheet is a live first-party implementation of the minimal layout: its iframe is block-level and nearly full width, capped to the viewport height;
.pdfuses an 8.5:11 aspect ratio, with a taller mobile ratio. The site’s design notes confirm that PDFs can be read in an embedded PDF viewer. This keeps the document in the reading flow without a heavy custom viewer. - For a basic embed, use a responsive
<iframe>pointing directly to the PDF, give it a descriptivetitle, and put a normal “Open/download PDF” link beside or below it. MDN’s iframe reference confirms that browsers can render PDFs natively and warns that an iframe has no fallback content if rendering fails; it also documents full-width CSS and theloading="lazy"option. - If fullscreen must be an explicit page-level control, place the frame in a wrapper and have a button call the wrapper’s
requestFullscreen(); toggle withdocument.exitFullscreen()when active. The Fullscreen API requires a user gesture and can reject, so retain the ordinary PDF link as fallback. If relying on a control inside a nested viewer, grant fullscreen permission withallow="fullscreen"on the iframe.
Sources
- Brittany Chiang, v4 personal-site source and live portfolio
- Julia Evans’s blog and first-party stylesheet
- IBM Developer Experience Guide: Typography
- Gwern.net design notes and stylesheet
- MDN:
<iframe>and MDN:requestFullscreen()
Related: Typography, Web Development.