Runic
LAYOUT

One text, laid out your way

Flip between top-down and left-to-right, pack branches tight, caption arrows, and let .back arrows route themselves around the boxes.

Try it free →Read the docs

What it is

Runic draws the diagram; you never place a box. The engine is deterministic, so the same document always produces the same picture, and the toolbar offers a few global choices instead of a thousand local ones. Slides want left-to-right; a wiki page wants top-down. Same text.

The toolbar

Flow direction switches between top-to-bottom and left-to-right; branches fan out horizontally in one and vertically in the other. Compact cards shrinks every card to 60% width (250 to 150 pixels for a step) and hides the icon chips, so big flows read denser; text wraps taller instead. Branch alignment centers branches under a decision, or keeps the first branch on the parent’s axis so a long main path reads straight (“Align left” top-down, “Align top” left-to-right). Tight packing, on by default, moves a sibling branch aside only where its boxes would collide with the arm before it, instead of reserving each arm’s full bounding box. Compact, alignment and packing are remembered in your browser once you have allowed Preferences in the cookie dialog; direction resets to top-down on reload.

Zoom runs from 25% to 250% in steps of 25; Ctrl/⌘ + scroll or a trackpad pinch zooms toward the cursor; click the percentage to type a value. Fullscreen hides everything but the diagram and returns with Esc. The sequence pane has zoom (50% to 150%), Fullscreen and Share only.

Captions

End a step line with a colon and a caption, Customer pays: payment confirmed, and the caption rides the outgoing arrow as a pill. The colon needs a space on at least one side, so https:// and 14:30 never split. It works on plain steps, .input, .wait, .fail, .do and .back; an .if cannot carry one, since branch arrows are labeled by their .then chips, and a .go takes no caption because its path ends. A caption on a path that ends has no arrow and is dropped. Captions tint violet in the editor.

Return arrows

.back <a few words of a step> draws a dashed arrow from the box above it to a step or .input anywhere in the document, earlier (a loop) or later (a skip ahead to a terminal state). The target is matched case-insensitively: a line whose whole text equals what you typed wins outright; otherwise the first line containing the words is used, plain steps searched before .input lines. .back Created: cancel order captions the arrow.

Right after a box — a step, input, Do, wait or fail card; notes and earlier .back lines are looked through — no card is drawn and the flow continues below, so several .back lines stack several arrows off one box with staggered captions. After a decision, a .go, an .end or at the very start of a document there is no box to hang the arrow on, so the .back draws its own card and that path ends there. Until the target text matches a step, a dashed hint pill beside the box shows what you typed with an ellipsis, or “loop back to…” while it is still empty.

Routes are orthogonal with rounded corners, through a gutter to the right (below, in left-to-right) proven clear of every node by a 14-pixel margin; parallel routes keep 14 pixels apart, several arrows into one box get staggered entries, a far-side target gets a direct arrow between the columns, and a self-loop draws a small out-and-around.

Limits

No manual placement, no per-node override. Empty branches show an “Add a step…” placeholder; an empty question shows “Type a condition…”. Left-to-right runs its own layout pass but reuses the same return-arrow router, transposed, so return arrows behave the same way in both orientations. Branch chips are coloured by label: yes, true and evet green; no, false, hayır and hayir red; everything else violet.

How to use it

  1. Flip direction
    Click the arrow button in the diagram toolbar (“Flow direction”). The flow re-lays out left-to-right; click again for top-down.
  2. Densify a big flow
    Click “Compact cards” for 60%-width cards. Tight packing is already on; toggle it to compare with roomy branches.
  3. Straighten the main path
    Click “Branch alignment”. The first branch of each decision continues straight from its parent; siblings fan out one way.
  4. Caption an arrow
    End a line with : caption, for example Order ships: within 24h. A pill appears on the arrow leaving that card.
  5. Add a return arrow
    Under any step type .back, pick a target from the menu, and add : label if you want a caption. A dashed arrow routes around every box.

Commands & shortcuts

Flow directionToolbar: top-to-bottom ↔ left-to-right (not persisted)
Compact cardsToolbar: 60% card width, icon chips hidden (remembered with Preferences consent)
Branch alignmentToolbar: center vs first-branch-on-axis (remembered with Preferences consent)
Tight packingToolbar: contour packing, on by default (remembered with Preferences consent)
step: captionCaption on the outgoing arrow; space beside the colon required
.back target: labelDashed return arrow to any step; exact line text wins, else first containing line
Ctrl / ⌘ + scrollZoom toward the cursor, 25%–250%
EscExit fullscreen

Tips

  • Left-to-right plus branch alignment reads like a timeline; use it for slide exports.
  • If two arms look crowded, toggle tight packing off to compare, then decide.
  • Keep captions to two or three words; they sit beside the arrow and do not reflow the layout.
  • Direction is not saved, so set it right before an export.
  • When two steps share words, pick the target from the .back menu so the line text is copied exactly; an exact match beats every longer line that merely contains it.

Questions

Can I move one box?

No. Every position is computed from the text. Change the order or nesting of lines, and use the toolbar toggles for the overall shape.

Why does my .if line turn pink when I add a caption?

Decisions cannot carry an arrow caption; each branch arrow is already labeled by its .then chip. Move the caption to the step before the decision.

Why did a .back become a small dashed pill?

Its target matches no step text yet. Pick one from the .back menu or type a few words that appear in the step; the pill becomes the arrow when it matches.

Why did my .back draw a card that ends the path?

It sits right after a decision, a .go, an .end, or at the top of the document, where there is no box to hang the arrow on. Put the .back directly under the step the arrow should leave from and the flow continues below it.