Typography
Type scale, rhythm, and readability standards for every Lumora module
This page defines practical type usage: heading hierarchy, body rhythm, utility text, and code typography. Use the playground to test family, size, weight, spacing, and line-height combinations before shipping.
1. Type Scale Matrix
Canonical heading and body scale used across page templates
Build observability for distributed systems
Alerts, incidents, and release timelines
Deployment pipeline summary
Body text defaults to a comfortable rhythm for long-form scanning. Keep paragraphs concise and avoid over-tight line spacing in cards.
Small label: 12 / 500 uppercase tokens for metadata and chips.2. Interaction Playground
Generate live typography recipes
3. Heading Rhythm
Map section hierarchy from page title to local card title
Incident Command Center
Primary page context and action framing.
Active Incidents
Critical services
4. Body and Numeric Text
Ensure readability while preserving numeric alignment
Keep operational narratives clear and concise. For dashboard notes, prefer short paragraphs with direct verbs and specific values.
5. Composition Patterns
Practical card and table pairings for production pages
6. Real-use Snippets
Copy-ready snippets for heading map, body style, and numeric text
<h1 style="font-size:32px;font-weight:700;letter-spacing:-0.01em">Page Title</h1> <h2 style="font-size:24px;font-weight:600">Section Title</h2> <h3 style="font-size:20px;font-weight:600">Card Title</h3>
<p style="font-size:14.5px;line-height:1.6;font-weight:400"> Keep body text concise and readable for scanning. </p>
<div class="u-font-inter" style="font-variant-numeric:tabular-nums"> 09:15:02 — 1832 requests — 99.94% </div>