Structure
Routing, controllers, caching, collections, users and sourced pages: when a site needs more than pages, views and fields.
A page that only shows its fields needs none of this. Reach for these when a site has URLs beyond its page tree, data that is not a page, logic in a view or visitors who sign in.
Routing
Router files map URL sub-paths to closures. A page's view picks the router.
Controllers
Inject data into a view at render time.
Collections
Items that belong to a page, such as comments or registrations, kept in a database of their own.
Users and Roles
Accounts, roles, and the dot-notation permissions that guard routes and templates.
Sourced Pages
Serve pages from an API, a database or any other source through the normal routing, template and editing pipeline.
Caching
Keep a page, a fragment or a region of a template on the server. Choose who shares an entry, what splits it and what clears it.