quarto-dev / quarto-dev/quarto-cli

Revisit header font sizes, vertical spacing, content width

Open
#5,066 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement html
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

  • Is the h3 font size too close to h2, dampening the visual hierarchy?
  • Is vertical spacing around headers too tight, making the text harder on the eyes and more difficult to scan? Particularly h2 and h3
  • May be a bug: there is no vertical space between h1 and the description when it's shown. I'd try 8-16 px
  • Is the header description font size too small? Reference designs (Nature, New York Times, Distill, and Tailwind) consistently used a slightly larger size than the base font size. I'd try 19px
  • With the base font size reduced from 20px to 17px, is the content width too wide? On a large display, reference designs are 600-750px, and Quarto is ~850px.
Suggestion

Here is a side-by-side comparison after making some of these changes. Left is original. On the right, I have:

  • Decreased h3 font-size from 23px to 20px
  • Increased h2 top and bottom margins from 34 17 to 49 24
  • Increased h3 top and bottom margins from 25.5 8.5 to 40 20.
image

cc @allenmanning @dragonstyle

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Review the existing header typography and layout styles, compare h1–h3 spacing, description sizing, and content width against the references and screenshot, and confirm the intended values with maintainers. Done means an agreed, consistent visual update.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.