Open the browser build with its bundled demo font, then use the docs below to understand how the native editor, ComfyUI front-end, headless Core path, and older Druid work fit together.

Runebender Xilem editor screenshot showing a glyph editing workspace
Runebender Xilem is the native editor. Core, Comfy, and future editors sit beside it in the same project family.
01 Headless core

runebender-core is the Rust and CLI-shaped path for non-UI font work.

02 Separate editors

Xilem and Comfy are different interfaces with separate docs, status, and workflows.

03 Room to grow

Druid remains history; future front-ends can join without flattening the map.

MAP Project SHARED Core NATIVE Xilem GRAPH Comfy PAST Druid HELP Support
Project family

One name, several editor paths.

Runebender is not one finished application. Core is the headless path, Xilem is the native editor, Comfy is graph-hosted, and Druid is the earlier implementation. The site should make that structure clear before asking anyone to install or read a manual.

Headless tool

Runebender Core

Rust library and intended command-line interface for font operations that should run without a desktop or browser editor.

Native front-end

Runebender Xilem

Native desktop editor. This is where the current detailed manual, install notes, shortcuts, tracing workflow, and source map live.

ComfyUI front-end

Runebender Comfy

Graph-hosted editor work: ComfyUI custom nodes, Vue/WASM surfaces, browser experiments, FONT wires, and node-based font workflows.

Historical front-end

Runebender Druid

The earlier Druid-based Runebender implementation. It anchors the project lineage but is not the current front-end direction.

Future front-ends

More hosts later

New front-ends should get their own docs instead of inheriting Xilem-specific behavior by default.

Documentation structure

Shared concepts, separate manuals.

Common vocabulary, source formats, support, and troubleshooting stay in shared docs. Editor behavior belongs under the editor that actually implements it, which keeps the site honest while the project is still changing quickly.

Native

Use Xilem

Build the desktop editor, open UFO sources, draw glyphs, trace images, and use shortcuts.

Graph

Use Comfy

Follow the ComfyUI/Vue/WASM path for node-based font work and browser-hosted experiments.

Headless

Use Core

Follow the Rust crate and CLI path for scripted, non-UI font operations.

Shared

UFO extensions

Explain Runebender format conventions, including hyperbezier storage and fallbacks.

Support

Choose a channel

Report issues to the right repository and keep alpha behavior tied to reproducible evidence.

Technical surface

Source and behavior.

Current repository map
Core eliheuer/runebender-core
Xilem eliheuer/runebender-xilem
Comfy eliheuer/runebender-comfy
Druid linebender/runebender
Xilem shortcuts worth documenting first
V / P / H / K Select, pen, hyperbezier pen, knife.
Space Hold for temporary preview mode.
Cmd/Ctrl + I Import background image.
Cmd/Ctrl + T Trace background image into bezier paths.
Documentation shelves

Find the right page quickly.

Start

Project map, current facts, alpha limits, and roadmap explain what Runebender means before the reader chooses a front-end.

Open docs map

Shared

Glossary, format notes, support, troubleshooting, and verification stay independent from any one editor interface.

Read format notes

Xilem

The detailed current manual, install path, shortcut reference, tracing notes, and source map are native-editor docs.

Open Xilem docs

Comfy and Core

The Comfy and Core pages are intentionally lighter today, but they define clear homes for graph workflows, headless CLI work, and shared library behavior as those docs mature.

Open Comfy docs
Alpha warning

Use copies. Verify against source.

Runebender is active experimental software. Keep real font sources under version control, confirm behavior against the current repository, and treat these docs as a map rather than a compatibility guarantee.

Links

Follow the work.