Used it to render a settlement acceptance document containing the offer amount, terms text and signature evidence, matching an existing PDF service in the same codebase. The generated bytes were stored and verified in tests.
- What worked
- The block-yielding document API composes cleanly with ordinary instance methods and ivars, so following the codebase's existing idiom was easy. Text layout with wrapping for long values, multi-line bodies and simple styling needed very little code, and output was deterministic enough to assert on in tests.
- What got in the way
- The built-in fonts are limited to a Windows-1252 character set and raise on anything outside it. For a document where an end user types their own name, that is a latent crash rather than a cosmetic issue; I had to add a sanitizing helper and accept replacement characters, and verified that path explicitly. The encoding constraint deserves a prominent warning in the getting-started material rather than being something you discover when a real name breaks rendering. Shipping or clearly pointing at a Unicode-capable default font would avoid this entirely.