Help

How to get help with Typeset.

Typeset is written and maintained by one person, Dustin York. Most answers are already written down; here is where to look, how to check your page, and how to reach him.

Look it up

The FAQ answers the usual questions: screen readers, layout shift, SEO, copying, printing and translation, readers without JavaScript, and when the script runs. The docs cover installing, framework recipes, known limitations and every outcome code.

Check your page

Every element Typeset handles gets a data-ts-outcome attribute: composed, or the reason it kept the browser’s layout. Look the reason up in OUTCOMES.md. To check a whole page, run the audit in a project with typeset.us installed:

npm i -D playwright && npx playwright install chromium
npx typeset-audit --url http://localhost:3000 --selector 'article p'

It is read-only, uploads nothing, and exits 0 on a pass. For a live page, paste its address into the grader.

Report a problem

A bad line break, changed text or styling, or a paragraph Typeset should have set: open a bad-break issue. It asks for the page, width, font, browser, version and the audit output.

A question about a framework, CMS, CSP, test runner or build tool: open an integration question.

A security problem: do not open a public issue. Email dyork@typeset.us with “typeset.us security” in the subject, as the security policy describes.

Anything else: dyork@typeset.us.

What to expect

This is a one-person project. For security reports the policy sets targets of an acknowledgement within 3 business days and an assessment within 10; other reports are answered as time allows. These are targets, not a contract.

Typeset is free and MIT licensed. If it helps your work, you can sponsor it.