visitor@baudelaire themes:~$

Maths, tables, and other things prose is bad at

1 min read[typst]

Curves fanning out from a baseline.

A typesetting language brings its own answers to the things Markdown farms out to plugins. None of the following is an extension; it is what Typst does.

An equation

The sum every incremental build is really computing, which is how much work it managed not to do:

saved = ∑ 𝑝 ∈ pages cost ( 𝑝 ) ⋅ [ 𝑝 unchanged ]

Inline maths sits in a sentence without ceremony: a page whose fingerprint ℎ(𝑝) is unchanged is served from the cache.

A table

Flavor Binary Drops
full about 40 MiB nothing
slim about 11 MiB fonts, JS, CSS, images, cards

A list that means something

  1. Parse the content tree and read every frontmatter.
  2. Fingerprint each page against the cache.
  3. Compile what changed, in parallel.
  4. Post-process the DOM: links, anchors, images, meta.
  5. Write, then sweep whatever no source maps to.