Add the auto-generated node catalog to the website's user manual (#3662)

* Generate the MVP node catalog in the manual (with some placeholders)

* Implement nearly the rest of everything

* Move to the tools directory and make it generate nicer default values

* Add category descriptions

* Organize file structure and improve type naming

* Improve book table of contents code

* Add collapsing chapter navigation to the book template

* Add to build workflow

* Clean up site structure
This commit is contained in:
Keavon Chambers
2026-01-20 22:52:03 -08:00
committed by GitHub
parent 5543afd44b
commit 7af60e02a3
61 changed files with 1131 additions and 384 deletions
@@ -5,7 +5,7 @@ page_template = "book.html"
[extra]
order = 2 # Chapter number
js = ["/js/youtube-embed.js"]
js = ["/js/component/youtube-embed.js"]
css = ["/component/youtube-embed.css"]
+++
@@ -3,8 +3,8 @@ title = "Editor structure"
[extra]
order = 1 # Page number after chapter intro
css = ["/page/developer-guide-editor-structure.css"]
js = ["/js/developer-guide-editor-structure.js"]
css = ["/page/contributor-guide/editor-structure.css"]
js = ["/js/page/contributor-guide/editor-structure.js"]
+++
The Graphite editor is the application users interact with to create documents. Its code is a single Rust crate that lives below the frontend (web code) and above [Graphene](../../graphene) (the node-based graphics engine). The main business logic of all visual editing is handled by the editor backend. When running in the browser, it is compiled to WebAssembly and passes messages to the frontend.