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

Build your first diagram

Place components from the palette, connect them with edges and name them, with or without an account.

A few minutes from now you will have a Grid with four named nodes (the cards on the canvas) joined by three edges (the arrows between them), in the order a request travels. It takes three moves, repeated: place, connect, name.

Where to draw it

You do not need an account. Try the editor — no account on the home page opens a real, editable sandbox with a small diagram already on it and a short list of free components. The steps below start from an empty canvas, so clear it first: press Ctrl/⌘+A, then Delete. The sandbox expires after two days unless you click the button on the sandbox itself (Sign up free, or Keep it in my account if you are signed in); signing in by itself does not save it. With an account, Create Grid on your dashboard starts an empty Grid, since Start from scratch is selected by default, with Diagram pressed.

Place, connect, name

  1. Place. Find Web App in the Components palette and drag it onto the canvas. Double-clicking it also works: the node lands at the centre of your view, or at the nearest spot where it overlaps nothing.
  2. Connect. Place REST API the same way. Hover over the Web App node until its handles show, press on one, drag to REST API and let go anywhere on that node. The arrow points away from the node you started on.
  3. Name. Double-click the Web App node, type Storefront and press Enter. Escape cancels.

Repeat with Application Service and Relational Database, connecting each one from the node before it as it lands, and name the other three Orders API, Orders Service and Orders DB. Double-clicking an edge opens its label the same way: label the three edges requests, calls and queries, in order.

Your first Grid, finished

All four are Architecture nodes; The node palette & component families explains the other families and when to use each. Any edge can be restyled later with Connecting & styling edges.

Names matter because a Challenge's AI evaluation reads them, and so does anyone else who opens the Grid. Naming nodes: inline rename & the inspector has the rest of what renaming can do.

When a move does something else

  • The node moved instead of connecting. You pressed the body of the card, and a drag from there moves the node. Only a handle starts an edge. Selecting & moving nodes covers the drag itself.
  • The line vanished when you let go. You dropped it on empty canvas, so no edge was created, and a notice tells you to drop it on a node.
  • Ten nodes still carry their catalog names. The reader learns what you used, not what each part does, so rename as you place.
  • Twelve loose nodes wait to be wired. Connecting them all at once is where diagrams turn to spaghetti, so connect each node as it lands.

The same rhythm on a real brief

The URL Shortener Challenge needs an account, and its palette holds only the components that brief allows, with room for 12 nodes. When you reach the Grid, place React and Express, connect React to Express, and rename Express after its job, such as Redirect API.

Practice this