How to use the Font Pairing Brief Generator.
A font pairing brief should connect type choices to reading conditions and licensing. Specify hierarchy, scripts and fallback behavior before choosing decorative combinations.
Make the workflow fit your task.
Define heading and body roles, reading sizes, required scripts and delivery constraints. Describe desired character and fallback behavior before choosing specific families. Compare representative text and verify licensing and loading requirements for any final selection.
- What you provide
- Brand tone, content needs and available fonts.
- What you get
- Typography pairings with hierarchy and licensing checks to perform.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Typography brief for an editorial website with English and French long-form articles. No specific font families chosen. Need headings, body text, fallbacks and license review.
Completed example
Body role: comfortable long-form reading at the actual article size, with clear punctuation and French diacritics. Heading role: distinct hierarchy without overly decorative letterforms. Test text: English paragraphs plus French accents such as é, è, ê, ç and œ. Implementation: define practical fallback stacks and inspect layout shift and loading cost. Selection gate: verify the chosen families' licenses and required weights before implementation.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a font pairing be chosen from an English-only sample when French is required?
Include accented characters and representative French text to check coverage, spacing and the intended reading experience.
Why does the page layout shift when the web font loads?
Fallback metrics may differ from the chosen font. Review fallback choices and loading behavior as part of the brief.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑