Fontra Workflow
A command-line tool for processing fonts in repeatable, declarative pipelines. Describe what should happen in a YAML file (read, filter, merge, write) and run it.
Work in progress
This section is new and still being written. The tool itself lives at fontra/fontra-workflow, whose README is the reference for now.
A first pipeline
# build.yaml
steps:
- input: fontra-read
source: MyFont.designspace
- filter: subset-glyphs
glyphNamesFile: latin-basic.txt
- output: compile-fontmake
destination: MyFont-Subset.ttf
$ fontra-workflow build.yaml --output-dir build
Recipes
Copy, paste, adjust. The fastest way to learn Workflow is to modify a recipe.
Subset a font for the web
Keep a glyph set, drop the rest, compile.
Extract a static instance
Pin Weight 700 and export the Bold.
Convert format
.glyphs → .designspace, TTF → .fontra, and so on.
Merge two fonts
Fold a symbols font into a text family.
Ship only finished glyphs
Filter by development status, then compile.
Cubic → quadratic + round
Production clean-up before export.
How it works
- Five step types:
input,filter,output,fork,fork-merge. - Lazy and pull-based: outputs pull glyphs through the chain; only what is written gets processed.
- Composable: every filter is itself a font, so any output can feed any input.
- Extensible: third-party actions register through an entry point (this is how
fontra-compileadds its compilers).
Action reference
Every action with its arguments, types and defaults, covering axes and designspace, glyphs and outlines, subsetting, features and kerning, and compilation.
All actions
The complete catalog, grouped by purpose.
Writing your own action
Subclass, override one hook, register.
Improve this page on GitHub
· This documentation is licensed under CC BY 4.0
· Built 2026-10-27