Expose more Typst orange book variables to YAML (Pandoc template)

Open
#14,270 0 comments 2 reactions 1 assignee View on GitHub

@gordonwoodhull is already working on this.

Since Mar 25, 2026.

Assessment

This issue has not been assessed yet.

Description

books enhancement typst

It would be good to expose as much as possible the options from the Typst Orange book template to avoid ease simple customisation to users without having them required to takes the typst-show.typ (kind of hidden) to make those, like changing the outline depth of the parts.

See the workaround requiring to be aware of typst-show.typ existence: https://github.com/orgs/quarto-dev/discussions/14269#discussioncomment-16314960

Discussed in https://github.com/orgs/quarto-dev/discussions/14269

Originally posted by stephenturner March 25, 2026

Description

I just read @cwickham's blog post on Quarto 1.9 and immediately turned one of my quarto books which rendered to HTML and PDF to now use typst.

Here's the repo: https://github.com/stephenturner/dstt

Here's the rendered book: https://dstt.stephenturner.us/Data-Science-Team-Training.pdf

In my _quarto.yml:

format:
  html:
    theme:
      - cosmo
      - brand
    code-link: true
    author-meta: "Stephen D. Turner"
  typst:
    theme: default
  epub:
    theme: default

(Side note question: the official docs show you can use format: typst, but doesn't show how to use typst with other formats, so I had to put the dummy theme: default under the typst heading).

Problem is my section heading pages attempt to put a mini TOC for that section, but the TOC bleeds off the pages.

Is there any workaround for this? Filing this here instead of an issue because I don't know if this belongs on Quarto, Typst, orange-book, or elsewhere.
quarto v1.9.36, MacOS 15.7.4.

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

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.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.