Limitless power to write, create, and automate anything that you can fit on a page.
Set the standard with automations and beautiful typesetting
Members of over 3,500 universities and laboratories and over 1,000 businesses are using Typst.
Write your content as markup with a focus on structure. No distractions.
= Introduction
Our concept suggests three
ways that A-Mail can be best
utilized.
- First is to reduce the
probability of the failure of
a space mission. This problem
is known as the Mars problem
and suggests problems with
human communication.
#figure(
image("a-mail.svg"),
caption: [
Visualization of the FTL
Earth-to-Mars
comms capabilities
enabled by A-Mail.
],
) Pick a template, create your own, or just start writing. All the formatting happens automatically.
Export as a PDF, image, or a website (in preview), without touching your markup.
Different documents have different needs. Typst supports common types of content out of the box while giving you the power to build the rest.
Visualizations. No matter whether a Gantt chart or an arrow diagram: Visualizations always stay up-to-date with your data.
Mathematics. With beautiful equations as a first-class citizen, Typst is ready for research.
Plots and charts. Box plots, contours, paths, or just a bar chart: Pick a package and draw just the right plot for your data.
Tables. Write tables by hand or plug in CSVs or JSON. Style them all at once or tweak them individually.
Code. Syntax highlighting, line numbers, themes, and callouts. Present code snippets just like in your IDE.
Bibliographies. Automatically format citations and references and sync with Zotero or Mendeley.
Slides. Take your content straight from the page to a slideshow. You can even present right from the app.
Anything else. Your own building blocks: With the integrated scripting features, the only limit is your imagination.
The tutorial sets you up to start writing in less than 30 minutes. And you can learn about advanced topics later in the reference.
Fuse content and scripting to make your documents reactive. In the realm of a Typst document, there is nothing you can’t automate.
= Markup <markup>
With built-in syntax for the most common document elements, Typst markup is designed to be pleasant to write and read:
- *Strong* and _normal_ emphasis
- A reference to @markup
- Math: $a, b in { 1/2, sqrt(4 a b) }$
But that's just the surface!
The compiler is a command line tool that turns Typst markup into PDFs, images, and web pages. It forms the basis of the Typst ecosystem, including our collaborative web app.
Charlie started running workshops, short sessions teaching players how narratives could be constructed, how inference worked, how to keep distance from a machine’s suggestions. The sessions were radical in their simplicity: teach people to see the scaffolding. Some attendees left offended—“why should I learn to defend myself from a game?”—while others thanked Charlie for giving them tools to navigate their own reactions.
Years later, Mind Games remained a touchstone in conversations about interactive narrative. It was studied, critiqued, improved, wound down, and forked in new directions. Some derivative projects abandoned the introspective ambitions entirely and made lighter, puzzle-first experiences. Others dove deeper into clinical collaborations, building interfaces that required licensed practitioners and careful protocols.
Mara suggested hardened controls: stricter opt-ins, clearer consent dialogues, and rigorous logs that could be reviewed. Charlie built them into the release—an explicit conversation at the start, confessional and frank: Mind Games learns from you; it adapts; it cannot read your soul but it can lean on patterns. Most players clicked through. Some lingered, reading the clauses as if reading a map to where they kept their keys.
Charlie Forde’s studio smelled like old coffee and solder. Sunlight from the high windows cut across racks of hardware and half-disassembled consoles, dust motes moving like tiny satellites. On a narrow bench beneath a wall of monitors, a single machine hummed quieter than the rest: an experimental rig Charlie had been refining for months, its chassis etched with careless doodles and the faint aroma of ozone. DigitalPlayground - Charlie Forde - Mind Games
The prototype’s art style intentionally toyed with the uncanny valley. Not chilling on purpose, but precise enough that familiarity thrummed underneath. NPCs remembered conversation fragments from prior sessions; objects carried faint continuity errors you could only spot after three or four playthroughs. The soundtrack was a collage of field recordings and fragments of ditties—enough to suggest motive, never enough to reveal it. Charlie believed omission could be a character in itself.
Charlie moved on, as creators do, to other puzzles and other portraits of human pattern-seeking. But they kept the brass key. Sometimes, in the quiet of their studio, they would boot the original Mirror and watch how naive sessions unfolded—players finding comfort in algorithmic empathy, or recoiling from it, or returning again and again. The machine hummed, impartial and precise, a testament to both possibility and restraint.
In the end, Mind Games taught a simple, stubborn lesson: tools that shape how we remember need not be forbidden to be treated with respect. They required guardrails, explanation, and consent—not as afterthoughts but as part of the design. Beneath the art and the code, beneath the small triumphs and the uneasy evenings, was a thrum of responsibility. Charlie kept listening to that thrum, and that listening became the truest part of their craft. Years later, Mind Games remained a touchstone in
Release day was small but intense: a drop on an experimental platform, a handful of streamers, a thread on a community board. Initial reactions split along a neat seam. Some players celebrated the way the game parsed their idiosyncrasies and reframed them into catharsis. One player wrote that the game had somehow coaxed them into saying goodbye to a relationship they’d been postponing, presenting memories in a sequence that made the farewell inevitable yet gentle. Another player sent a blistered message about how the game suggested the exact phrase their father used before leaving—the phrase had been private, uttered only once. Charlie’s stomach sank at that one.
A pivotal moment came when Alex, a longtime friend and occasional playtester, reported something Charlie hadn’t programmed: an emergent motif the engine had spun from Alex’s own history. Alex had described, later in a message, a recurring childhood lullaby that had been long forgotten. Mid-session, a distorted fragment chimed in the background—an accidental echo, Charlie assumed. Alex swore it matched exactly the lullaby their grandmother sang. Charlie combed through logs and code. There were no samples matching that melody. The engine had extrapolated from Alex’s input—phrases, timestamps, even the cadence of their pauses—and constructed a melody that fit the patterns. It wasn’t a copy; it was a ghost of memory constructed from algorithmic inference. The thrill and the ethical rustle of unease arrived together.
Those revisions calmed some criticisms and birthed new appreciations. Therapists and narrative designers began to engage, simultaneously fascinated and cautious. A therapist friend pointed out the potential: guided carefully, Mind Games could be a tool for exposure, rehearsal, and reframing. But the same friend warned about unmediated use—untethered activation of dormant memories could destabilize. Charlie integrated a “companion mode” where players could opt into a slower pace, with prompts designed by clinical partners, and safe exit points more frequent and explicit. pragmatic and unfinished
The moral complexity never purified. New reports kept emerging—some banal, some haunting. One player reported that the engine’s insistence on a particular memory reframed their recollection until they could no longer separate the game’s narrative from what had actually happened. Charlie read it, the line breaks like small splinters in the margin of their ethics. They realized informed consent required not just an opt-in but an ongoing literacy: players needed to understand how machine inference works—what it means to have your memory mirrored, amplified, or suggested.
The project had started as a personal experiment. Charlie had been studying cognitive heuristics and how people fill gaps—how the brain leans on pattern and expectation when data is scarce. What if a game could exploit those instincts, nudging players toward truths by offering alternatives so plausible they blurred with reality? Mind Games would not simply present puzzles; it would reframe the player’s own memory and decision-making, encouraging doubt and then offering an anchor, only to pull it away.
Charlie was small, quick-handed, and habitually late for everything except breakthroughs. They kept a cardigan with ink stains and a necklace with a brass key that fit nothing in the room but hooked somewhere in their ribcage. Where other developers chased glossy releases and sponsorships, Charlie chased puzzles—systems that resisted easy answers. Mind Games was their obsession: a layered interactive narrative meant to feel less like a finished product and more like a conversation with something that knew you too well.
The audit was perfunctory, handled by a recommended security consultant named Mara. She was precise, dry, and suspicious of elegance. They met in the studio with its river of cables, and Mara asked clinical questions: data retention, anonymization, third-party calls. Charlie answered honestly, aware of how The Mirror ingested data. Anonymized? Mostly. Aggregated? In design. But the concern gnawed: the engine’s inferences could approximate personal memories. How much should a game be allowed to guess?
At night, Charlie walked riverside and thought about what design responsibility meant in a world that could reconstruct you from fragments. If mind is pattern, and pattern is data, how much stewardship should the creator have over the reflections their mirror casts? The answer, pragmatic and unfinished, was protocol. Charlie expanded the consent flow into a layered dialogue: an onboarding that explained potential outcomes in plain language, a mid-session “pulse check” that asked if the game’s direction felt comfortable, and a simple “reset” mechanic that would scrub session-specific inferences from short-term memory. They also added human oversight—if the engine’s inferred content matched sensitive categories—loss, trauma, identity shifts—it would flag for review and avoid escalating without explicit permission.
Automatically convert Word, LaTeX, Markdown, or OpenDocument Text files to Typst projects on your dashboard.
Use one of the 1100+ community packages and templates on Typst Universe. Browse the available categories below:
Our web app is the best place to use Typst and collaborate on projects. The Free Plan is rock solid, and Typst Pro takes you even further.
Typst is designed for secure, reliable, and scalable operation in big and small organizations.

A 2000-page contract note takes approximately 1 minute to compile with Typst, in stark contrast to lualatex’s 18 minutes.
Learn more about us and our journey to build a new foundation for document creation.