Tutorials

Learn by path.

These are short learning sequences for the alpha app. They borrow the useful parts of mature font-editor docs: start with one concrete task, keep the path visible, and send readers to reference pages only when lookup detail is needed.

StatusAlpha tutorial index
AudienceFirst-time users, testers, contributors, agents
SourceWebsite docs and Runebender Xilem README
StabilityLearning goals are stable; command details may move

Get started

Use this path when you want to see the editor running and open a real UFO source.

  1. Read Current facts and Alpha limits.
  2. Follow Install and run.
  3. Open assets/untitled.ufo from the source repo.
  4. Use Xilem shortcuts only for shortcuts you need immediately.

Draw and edit

Use this path when you want to understand the editor surface without memorizing every command.

  1. Read Drawing for the tool names and contour model.
  2. Try Select, Pen, Hyperbezier Pen, and Knife on a disposable UFO checkout.
  3. Use preview, fit, and zoom while judging shape and spacing.
  4. Check Capabilities for what is documented versus still moving.

Trace an image

Use this path when you are testing bitmap-to-outline workflows.

  1. Read Tracing.
  2. Import a background image and align it to the glyph metrics.
  3. Use local img2bez tracing first when offline reproducibility matters.
  4. Use QuiverAI only when cloud tracing and API credentials are acceptable.

Understand the format

Use this path when you need to reason about source files and compatibility.

  1. Read Format notes.
  2. Use Glossary for terms like UFO, GLIF, cubic, and hyperbezier.
  3. Use the source repository spec for exact hyperbezier storage details.
  4. Treat website docs as orientation unless the linked source says otherwise.

Work on the app

Use this path when you are an agent or contributor trying to locate code responsibly.

  1. Read Development for the project model.
  2. Use Source map to find likely implementation areas.
  3. Check Workflow paths before changing user-facing docs.
  4. Update llms.txt and llms-full.txt when the public docs map changes.