PensaGrex · tree grammar study
One skin for all ten, so the only difference is the layout language itself. Every panel shows the identical HomeLab forest: a done setup, an in-progress step that holds the branch cursor, then a three-way fork — a to-do with a note, an in-progress sub-stack, and a cancelled dead end.
Sideways node-link
Parent on the left, children fan out to the right on elbow connectors. The org chart, turned on its side.
Gantt swim-lanes
One lane per branch, tasks laid left to right in order. A fork drops new lanes at the split column, tied back with a bracket.
Subway line
Each branch is a continuous track; tasks are stations along it. A fork peels new parallel tracks off the split point.
Miller columns
One column per depth; open a task and its children appear in the next column. You drill a single path; the forest lives in column one.
Icicle partition
Space-filling bands: a task's height is its share of the subtree; children sit flush to its right. No connectors — adjacency is parentage.
Org-chart tree
Parent on top, children below on elbow connectors. The familiar top-down tree.
Indented outline
A file-tree list: indentation is depth, guide lines join parent to child. The densest, most text-forward option.
Commit graph
A git-style rail on the left carries the branching; the task details sit in an aligned list on the right.
Flow split
A single trunk drops down; at a fork a distribution bar splits it into parallel stacks, each continuing on its own.
Nested boxes
Children are drawn inside their parent; depth reads as containment. A fork is one box holding several.