Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Naming nodes: inline rename & the inspector

Double-click to rename a node where it sits; open the Node Inspector when it also needs a service type, a description or a color.

Rename it where it sits

Double-click a node and a text box opens on its label. Type the name and press Enter. Escape closes the box and keeps the old name, and clicking anywhere else saves what you typed. This is inline rename, the quickest way to label a node.

Try it: double-click this node and type a specific name like "Orders API".

  • Keyboard. With the canvas focused, Tab moves from node to node, and Enter or F2 opens the same box on the focused one.
  • Length. A name holds up to 80 characters on one line, so a line break you type turns into a space.
  • Shapes, frames and comments. The double-click edits their text rather than a title.
  • Edges. Double-clicking one edits its label in the same way; the rest of edge styling is in Connecting & styling edges.
TipA node's display name falls back to its catalog title until you type your own — so a node you have not named still reads sensibly, but a specific name reads better.

When a node needs more than a name

Click a node to select it and the Node Inspector opens in a side panel, where you can edit the title plus service type (subtitle on pattern nodes), description and color. If it is missing on a diagram Grid, look for an open panel such as Explain or Snapshots: that panel takes the inspector's place until you close it. On challenge Grids the inspector is hidden, so inline rename is the way to label.

For the title alone, double-click is the fast path. Save the inspector for service type, description and color.

Names that tell the reader something

A node's icon and shape already say what kind of component it is. The name is where you say what it does in this design, and other features read it: hints and evaluations on a challenge Grid refer to your nodes by their on-canvas names, and Ctrl/⌘+F finds a node by its name (see Working faster: shortcuts, search and tidy). Two habits waste that:

  • Names that restate the type. "PostgreSQL" on a PostgreSQL node adds nothing, because the icon says so already. Say what it stores: "Orders DB".
  • Generic numbering. "Service 1" and "Service 2" force every reader to reverse-engineer the design, and leave the AI feedback talking about "Service 2". Name the responsibility: "Checkout Service", "Pricing Service".

Name a whole design before you wire it

Naming is easiest to practise on a challenge Grid, where inline rename is the only way to label. In the URL Shortener challenge, place every node first and give each one a title that says its role, before you draw a single edge. The AI evaluation reads your labels, so read the score feedback for one thing: whether it quotes your names in sentences that make sense on their own. How Challenge Mode works explains where that feedback comes from.

Practice this