Notebook basics
A GUIDE notebook is designed around one lens: three columns that always mean the same thing, with a history built to be versioned, diffed, branched, merged, reviewed, and cited.
A GUIDE notebook is designed around a single authoring surface, not a set of switchable views. On the left, a unified timeline is meant to make provenance spatial — every entry and edit as a row you can filter and jump to. In the center sits the notebook itself: a stack of cells, the one place work happens. On the right, a contextual inspector is designed to stay quiet until you select something, then surface that cell's dependencies, staleness, and any relevant tools or widgets. This is the layout GUIDE's notebook is built toward; treat it as the design, not a screenshot of a finished screen.
A notebook in GUIDE is designed to be version-controlled the way a codebase is. See GitHub for Science for the full version/diff/branch/merge/review/cite framing this notebook is built toward — it's a 5-year architectural direction, not a claim that full git-style branching and merging works today.
This page describes how GUIDE's notebook is designed to work, conceptually — it isn't a walkthrough of your own signed-in workspace or its current contents. For account-specific help once you're working inside GUIDE, look for in-product help rather than this page.