Pages
Sources
Docs: Ponder Primer and Panes Web App: Open a Composed Parable, select Pieces, and choose a Page from the unified tree. Home is a real placement Page and remains visible beside the other Pages, including before additional Pages exist. A Page is a major destination in a Composed Parable. It gives people a stable place to read, explore, or complete work, and it is composed entirely of Panes. A Page has code, capped at 4 KiB, and a Perception that lists the Panes it renders; it holds no data and no SQL of its own. Anything with data belongs in a Pane. Every Parable has a Home Page. Additional Pages can sit beneath another Page to form clear navigation without turning every small region into a destination. The Pages tree retains Home and the existing Page hierarchy. Direct links keep their stable Page identities. Above the content, the breadcrumb shows the path to the selected Piece, followed by a separate description band. The context selectors share the available width and wrap onto another row when their labels need more room.Build a Page
1
Name the destination
Use a short label that tells a reader what they will accomplish there.
2
Describe its job
Explain the outcome before adding controls or implementation detail.
3
Declare its Panes
Add each Pane the Page renders to its Perception. The Page’s code may
import only the Panes it declares, the foundation, and the sandbox runtime
packages; an undeclared import is refused at save.
4
Preview the complete route
Check navigation, empty states, keyboard use, theme, and the supported
viewport sizes. A Page that declares no Pane yet shows an “add a Pane”
placeholder and can still be saved.
5
Review the Patch
A Page that still declares no Pane, or declares a Pane that no longer
exists, is reported as a finding when the change is published.