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

Connecting & styling edges

Direction, labels, colour, routing styles and draggable bend points, and what a Challenge Grid leaves you.

A line joins an API to a queue, with no arrowhead and no words on it. Does the API enqueue, consume, or only monitor? Nobody opening your Grid can tell. An edge connects two nodes; what makes it useful is saying which way and what for. If you have not drawn one yet, Build your first diagram has the first connection.

Labeled, directed edges

Which way it runs

Every edge runs from a source node to a target node, with an arrowhead at the target by default, and Traffic Simulation follows that direction.

Select the edge and the Edge Inspector opens. Source Endpoint and Target Endpoint set what is drawn at each end: arrow, dot, none, or a notation marker, such as UML generalization or the entity-relationship crow's foot. Edge Style set to bidirectional puts an arrow on both ends and locks those two controls. Where flow matters, keep an arrowhead that matches reality.

Watch outEndpoints change the drawing, not the edge. An arrow moved to the source end looks reversed, while the edge still runs from source to target, and that is what the simulation reads. To turn an edge around, press Delete and draw it again from the other node. When the check at the top of the Inspector thinks an edge is backwards, it can offer Reverse Direction instead.

To rewire one end, select the edge and drag that end onto another node.

One word on the line

Type in the Inspector's Label field, or double-click the edge and type on the canvas. One word usually settles it.

Colour and the rest of the style

Color, Thickness, Stroke and Animation change only how the edge looks, so a dashed line means only what your Grid consistently uses it for. Calls per upstream request (how many calls each request at the source node makes over this edge) and Caller's deadline, in the same panel, are inputs to the simulation that Checking a diagram: Explain and Simulate introduces.

Getting a line out of the way

A line ploughing through a box reads as a connection to it. Line Shape sets the edge's routing: curved (the default), squared or straight. Try switching it first.

Need an edge to bend around a node? Select it and drag the handle at its midpoint to add a waypoint (bend point); drag the waypoint to reshape, double-click it to remove it, or right-click the edge → Reset shape to clear them all. When many edges fight for the same space, the layout is usually the problem rather than the routing: see Organizing large diagrams: frames, groups & annotations.

What a Challenge Grid leaves you

A Challenge Grid hides the Inspector and turns waypoints off. Double-clicking an edge to edit its label is the only edge setting you can change: the direction is the one you drew, and a wrong one means deleting the edge and drawing it again. An edge leaving a flowchart Decision starts out labelled from its port, yes or no.

Read a flow aloud

Open the User Login Flow Challenge, whose scoring asks whether decision conditions are correct and labelled, and whether the flow is unambiguous. Direct every edge, label each one leaving a Decision with its condition, and label any other whose nodes leave it unclear. Then read it aloud, edge by edge, from Start to each End. If an edge does not make sense read out, check its direction and its label.

Practice this