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

Presenting a Grid: walkthroughs and scenario overlays

Mark one story on the Grid with a scenario, or drive a saved tour of it with a walkthrough, without making a copy.

"What happens when a user signs in?" Your Grid holds that answer along with every other one, which makes it terrible at giving just one. Two tools narrow it down in the meeting, and which you reach for depends on the question:

  • "Which parts are involved?" A scenario overlay is a named lens: it highlights the elements one story touches and dims others you choose, all at once. Use it to isolate: "this is the checkout path, everything else greyed."
  • "In what order?" A guided walkthrough is an ordered set of saved steps, each one a camera position, a set of highlighted elements and a caption, played back over the live Grid, over time. Use it to narrate: "first the request arrives here, then…"
NoteCreating and editing scenarios needs Pro or higher on the Grid owner's plan; showing and deleting existing ones does not depend on the plan. Walkthroughs need Premium, resolved from the Grid owner's plan, so a guest on Free or Pro invited to a Premium owner's Grid can watch and follow the presenter. Sharing & realtime collaboration covers the invite. A template's own source Grid offers neither tool.

Mark a story with a scenario

  1. Open Scenario overlays in the editor's top bar and choose New scenario.
  2. Name it after the story, select the elements it touches on the canvas, and press Highlight.
  3. Select what should fall back and press Dim. Nothing dims by itself: an element you leave unmarked stays at full strength.
  4. A new scenario is already showing. Press a row in the list to show that scenario, or the row that is showing to turn it off; Clear overlay also turns it off.

On a crowded Grid, Ctrl/⌘+A and Dim first, then select the story and Highlight: a new mark replaces the old one. Notes attach to the selected node or edge, or to the Grid when nothing is selected, and appear in the panel, not on the canvas.

Scenarios dim and never hide, because a reader needs to see what you left out to trust what you left in. Showing one is also shared: everyone on the Grid sees the same overlay, it needs edit access to switch, and it stays on until someone clears it, including the next time the Grid opens. Clear it when the meeting ends.

Drive a tour with a walkthrough

  1. Open Guided walkthroughs in the top bar and choose New walkthrough.
  2. Pan and zoom to the first view, select anything it should highlight, and press Add step from current view.
  3. Give the step a title and, if you want, a note. On screen sets its seconds, from 1 to 60; left empty, the step takes the walkthrough's pace of 5 seconds.
  4. Repeat, then press Restart: adding a step leaves you on the last one, and from there the button plays from the first step. On an earlier step it reads Resume and continues from that step, and after you stop it reads Play. Pause holds a step while you talk about it, and the previous and next buttons move by hand.

Steps should mark the turns in the story, not the stops. If every node gets a step, you have rebuilt the Grid in slideshow form. A step's camera is saved as it was, so after the design moves, open the step and use Replace saved view.

Playback moves only your own camera. Others stay where they are until they open the same panel and press Follow beside your name, where the list says who is presenting and on which step. A follower's camera then tracks yours, with the step's title and the count on their panel. The note sits in the step list, so put what the room needs to read in the title. To dim for everyone while you present, show a scenario first.

Neither one forks your Grid

A scenario stores emphasis and notes, never structure. A walkthrough stores camera positions, highlights and captions. Duplicating the Grid for the meeting instead gives you a copy that diverges the moment someone edits the original.

One Grid, several stories in it

Sign-in and feed-loading share only Web App here. Two scenarios hold both stories on one Grid, and an edit to Auth is there whichever one you show.

Neither tool keeps an older version of the design: for what changed since the last review, see Snapshots: comparing a Grid with its past self. A region that deserves a name all the time, not only in the meeting, wants a frame, from Organizing large diagrams: frames, groups & annotations.

Read and write paths on one Grid

Draw your design for the News Feed Challenge on a new Diagram Grid, on Pro or higher, since the Challenge's own Grid has neither tool. Build one scenario for the read path, a follower fetching a cached feed, and one for the write path, a new post reaching followers. Then show each in turn: a first attempt usually highlights far too much, and if anything the story never touches is still bright, dim it.

Practice this