satellite and bundle

document(...) — Typst’s own primitive for naming one output of a bundle compile — cannot be nested inside another document(...) call. That rules out letting several independent pieces of code each call document(...) on their own: whichever runs second would be trying to nest its document inside whatever the first one already produced. contexture.bundle is the fix: the only place that ever calls document(...). Anything built on contexture instead exposes a small constructor that returns a satellite(...) value — inert data, not a document(...) call — and the author lists as many of those as they like under one shared documents:, exactly as the quickstart above already did with glossary.

satellite(name, render:, applicable:, side-content: none)

describes one document to build alongside the manuscript. name is the base filename (bundle appends the variant/preview suffix, see next chapter). render() -> content produces this document’s content, called only when applicable() -> bool (default: always) says yes for the current compile.

bundle(template:, documents: (), strict: false, manuscript-name: "manuscript", body)

the pilot itself, called via #show: bundle.with(...) — body is the rest of the document, typically #include "manuscript.typ". Builds the manuscript (template(body)) plus every satellite whose applicable returns true, each as its own real document sharing this one compile’s introspection space with all the others.

manuscript-name: is the only thing that decides the manuscript’s output filename — it has no connection at all to the name of whatever .typ file you actually run typst compile on (every example in this manual compiles the snippet file shown directly, e.g. bundle-glossary-basics.typ, and still produces manuscript.pdf). A project that keeps its manuscript’s prose in its own file, #included into body, is free to name that file anything — calling it manuscript.typ is only a common convention, not a requirement bundle() checks for. Every example in this manual takes the simplest route instead: the file you see printed is the file compiled, with the manuscript’s own content written directly after #show: bundle.with(...), no separate #include at all.