Development
Develop Runebender.
Runebender development now spans shared Core code, the Xilem native editor, the ComfyUI front-end, and historical Druid context. This page points contributors at the moving parts.
| Status | Contributor orientation |
|---|---|
| Audience | Developers and documentation agents |
| Source | Runebender Core, Xilem, Comfy, and Druid repositories |
| Stability | Architecture notes are intentionally high-level |
Current status
The project family is very alpha and actively under development. Public docs should preserve that bluntness and avoid over-specifying unstable behavior.
Contribution paths
- Use eliheuer/runebender-core for headless CLI work, shared editing state, and data model work.
- Use eliheuer/runebender-xilem for the native editor front-end.
- Use eliheuer/runebender-web for the browser editor (Vue/WASM) — this is what the cloud editor on this site is built from.
- Use eliheuer/runebender-comfy for ComfyUI nodes and graph workflows; it imports the editor from runebender-web.
- Use the Support page to choose the right channel for issues, pull requests, and discussion.
- Keep format and architecture notes close to code until behavior stabilizes.
Docs backlog
| Project map | Use Project map for the current family structure. |
|---|---|
| Xilem architecture | Use Xilem architecture for the current native editor subsystem map. |
| Tests | Use Verification for current website and source checks. |
| Roadmap | Use Roadmap to separate documented behavior from future-facing work. |