Runebender

How-tos

Workflow paths.

Short paths through the alpha documentation. These are intentionally broad: they help people find the right page without pretending the UI is finished.

StatusTask map
AudienceEarly users, contributors, agents
SourceRunebender Xilem README and website docs
StabilityPaths are stable; exact UI details may move

First run

  1. Read Current facts so the alpha status is clear.
  2. Follow Xilem install to clone and run the native editor from source.
  3. Open a UFO such as assets/untitled.ufo.
  4. Use Xilem shortcuts for the current shortcut map.

Edit a glyph

  1. Use Drawing to understand the available tools.
  2. Use Select, Pen, Hyperbezier Pen, or Knife depending on the contour work.
  3. Use preview and zoom commands while checking shape and spacing.
  4. Keep real UFO sources under version control while testing alpha behavior.

Trace a drawing

  1. Read Tracing for the image import and autotrace workflow.
  2. Use img2bez for local/offline tracing.
  3. Use QuiverAI only when network access, API key, and API credits are acceptable.
  4. Expect traced outlines to need cleanup and metric adjustment.

Inspect format behavior

  1. Read Format notes for the conservative UFO and hyperbezier map.
  2. Use the canonical hyperbezier spec in the source repo for exact details.
  3. Use Glossary for terms like GLIF, contour, on-curve, and cubic.
  4. Prefer source links over copied specs when documenting behavior that may change.

Contribute

  1. Read Development for contribution entry points.
  2. Use Source map to find the relevant implementation area.
  3. Keep docs broad unless behavior has stabilized in code.
  4. Update llms.txt and llms-full.txt when documentation structure changes.