Choose your path
Start with the outcome you need. You do not need to read the reference from beginning to end.
| Your goal | Start here | Check before moving on |
|---|---|---|
| Understand Pagelove | How an application fits together | Identify the stored source, composed view, editable draft, and save request. |
| Set up a hosted site or coding agent | Onboarding | Find your public site and its separate authoring connection. |
| Finish a small working example | Build a shared note | Save, reload, provoke a conflict, and retain both versions for review. |
| Explore fragment editing | Shopping-list tutorial | Follow the incremental examples, then add the save/recovery checks from the shared-note guide. |
| Compose views from records | Blog tutorial | Distinguish a rendered view from the source you edit; review its stated limitations. |
| Control writes | Check permissions and validation | Exercise a refused write as well as an accepted one on the application endpoint. |
| Publish an update or restore content | Update and restore a document | Preserve the stored copy and refuse a restore based on an old validator. |
| Diagnose an unexpected result | Troubleshooting | Record the actual response and stored outcome before retrying. |
| Operate the platform itself | Operator documentation | Identify the deployed release, configuration, privileges, and recovery procedure. |
How the sections fit together
Getting Started is the short introduction and first HTTP example. Onboarding covers setup. Learn explains concepts through guided examples. How-to guides solve individual tasks. Reference defines the contracts those tasks depend on. Languages documents each execution context and its available tools.
For a specific HTTP method, schema field, or DOM member, go directly to its reference page. A short member page may inherit its contract from a linked base interface; a tutorial needs prerequisites, runnable steps, observable results, and recovery guidance instead. See verification and versions for how to judge applicability.