Eval Labs typography should make source truth easy to scan: strong headings, readable body text, restrained captions, and calm spacing.
Overall rhythm
Eval Labs docs should feel:
They should not feel like:
Headings
Headings should be direct and useful.
Good:
Weak:
Body text
Body text should be normal reading size and dark enough to feel like primary content.
For the homepage Logo/Text Table, the right-side copy should read as body text, not subheading text.
The relevant CSS knobs are:
Captions
Captions should be short, italic, and factual.
Good:
Avoid long captions that become paragraphs.
Code blocks
Use code blocks for:
- exact prompts
- JSON examples
- route names
- environment values
- repeatable workflow loops
Do not use code blocks just to make ordinary prose look important.
Callouts
Use callouts when a point needs to stand apart from normal prose.
Do not make every paragraph a callout.
Recommended use:
Other useful types:
Screenshot rhythm
Screenshots should support the workflow, not dominate it.
Best pattern:
Keep screenshot captions plain.
Eval interaction visual rhythm
The review interface should feel calm, guided, and native.
For scoring controls, prefer:
Avoid:
Visual rhythm is part of evaluation quality because it affects reviewer fatigue and confidence.
