Nodes and types
A node is either a shape with text or a typed card with fields. A type is workspace data: it can be edited and created in the Types tab without code, and it travels with the bundle and with copied nodes.
Every node has a position and size, a layer, z order, visibility, nesting inside groups and cards, and a style: colour, stroke, radius, shadow, gradient, opacity.
Basics
| Node | What it is |
|---|---|
| Rectangle, ellipse | shapes with text; font size, weight, alignment and colour in the style |
| Note | a sticky comment |
| Markdown | a block rendering markdown: headings, lists, checkboxes, code, quotes, links |
| Image | the file goes to the server as an attachment; the fit field controls fitting |
| Attachment | any file; zip is read entry by entry without unpacking |
| Group | a container with or without a frame; drags with its children, can grow to fit and lay children out on a grid |
| Link, mirror | a reference to a node and a live copy of a node elsewhere |
Diagrams and glyphs
Flowchart shapes: process, decision, data, database cylinder, hexagon, document, arrow, star, speech bubble, bracket. Nineteen vector glyphs with a caption: person, people, server, database, cloud, router, switch, firewall, client, mobile, sensor, gear, lock, shield, document, folder, mail, clock, bolt. The glyph changes in the inspector, and glyph plus a card with fields plus Save as component gives you a stencil.
Structures
| Type | Fields |
|---|---|
| Table | name, comment, fields as child nodes with type and key, indexes; foreign keys are reference edges |
| File, directory | name, extension, size, tree of entries |
| JSON object, JSON field | properties, key, value type, children |
| URL, contact, access | links, phone and e-mail, host and login |
| Task | number, title, description, status |
| Class, interface, function, member | UML-style code modelling |
| Task tree | tracker import with statuses |
| arch types | page, endpoint, component, service, queue, external system |
Values and computation
Values flow along binding edges into a specific card field. Recalculation is automatic; computed nodes have ok and error: an error does not hide, the node turns red and names the reason.
| Node | What it does |
|---|---|
| Value, value card | a constant: string, number, boolean, JSON |
| Operator | arithmetic and comparison |
| JSON Parse, JSON text | text to object and back |
| Get Path | a value by a path like users[1].name |
| Filter List, Map-Select, Predicate, Length | list selections |
| Aggregate | sum, min, max, avg, count by a path inside an element |
| Index, entries, object, Collect | reshaping structures |
| Watch | show the incoming value |
| ƒ in, out, call | your own functions as sub-diagrams; ƒx in the command palette builds a diagram from an expression |
| SQL Select, Where, Join, Insert, Update, Delete | SQL assembly by dialect, chained through next |
Documents
Blocks: title, chapter, epigraph, quote, list, code. The Manuscript assembles them by list rather than by coordinates, and ${path} substitution takes values from nodes. Output is markdown or a single self-contained HTML file ready to print.
Components and compact view
Save as component in the context menu puts the selection into My components; publish to server makes it shared for the team. Cards have two ways to shrink: collapse to the header and compact view without empty fields. Data is untouched either way.