Pages
A Page is a composed learning document — the unit you build in the Studio's page editor when you want to present material in a specific order and narrative, rather than letting a reader navigate the node graph on their own. A page is a sequence of blocks, and each block is one of:
- Markdown — plain prose, headings, math
- Node — embeds a node (optionally a specific facet of it) inline
- Facet — embeds a single facet directly, without the rest of its node
- Problem — embeds a practice problem
- Component — an interactive component, configured through the block editor's form (or raw JSON, for components without a custom form)
- Divider — a visual section break
Because a page is just an ordered list of these blocks, building one is mostly about sequencing: introduce a concept with a markdown block, embed the relevant node, follow it with an example facet or an interactive component, then a problem to check understanding.
Referencing and stability
When a page embeds a node, facet, or problem, that reference can optionally pin to a specific revision of the target rather than always showing its latest version. This matters for stability: if you want a page's content to stay exactly as you left it even after the underlying node is later edited, pin it. If you want the page to always reflect the current version, leave it unpinned. Each block can set this independently.
Pages vs. embedding directly in a node
If material is genuinely about a single concept, it usually belongs as a facet on that node instead of as a page — that way it's discoverable from the node itself and reusable across any page that embeds the node. Reach for a page when you're composing a sequence across multiple concepts, with your own narrative and ordering, the way a lecture or a chapter would.
Courses are built from pages
A Course is an ordered collection of pages with its own metadata — see that page for how pages compose into a full course.