NodlumeBuilding blocks
Page nodes
Plan pages as canvas nodes and turn them into Next.js App Router routes — set a path explicitly or let Nodlume derive one from the node title.
Page nodes are the routable surfaces of the application. They live in the Structure tab's Routes view, which is the only view that edits its own nodes rather than annotating the route tree — sketching the route tree is where a plan usually starts.
Paths
Each page becomes one route with its own file. Nodlume derives the path from the node's title — a trailing "page" is stripped and the rest is slugified, so a node called "Projects page" maps to app/projects/page.tsx. Set a path on the node when you want the route spelled out explicitly instead, and the inspector always shows the exact file the node will generate.
Arrange pages as parents and children to build the route tree. The root route cannot be deleted, so a project always has a valid starting point.
Dynamic segments and companions
A page's segment kind is chosen from a list rather than typed as brackets: static, param ([postId]), catch-all, or optional catch-all. Renaming the route renames its param with it, and the params a page receives are derived from its ancestors, never declared twice. Per route you can also add the App Router companion files — loading.tsx, error.tsx, and not-found.tsx — and group a level of siblings into a (group) segment, the organizing moves the App Router architecture checklist walks through.
What a page connects to
Edges leaving a page describe where a user can navigate from it, drawn in the Nav view — they become real <Link> elements in the generated file. Components and stores attach to pages from their own views without leaving the shared graph, and layouts above a page wrap it automatically.
A role guard on a page is a fact about the page, not the link that reaches it: guarded pages generate a real role check that redirects, and the guard shows up as a derived denial in the Security matrix.
Other targets
On non-web targets the same node becomes that platform's equivalent surface — an Expo Router screen on Mobile, an Ink screen on Terminal, or a browser-extension view on Extension. The tree you draw is the same; only the emitted files change.