API

A page whose view comes from an addon, resolving its views from the addon folder rather than the site.

The application core.

Every item of one collection field - data with no URL of its own, like comments, likes or tags - in a SQLite database at data/collections/{field}.db.

A field definition - its type, label, options and render template.

How one kind of field encodes, decodes, validates and indexes a value.

A field as one record holds it: the value with its definition (type, label, options) and where it lives (context).

One entry of a collection field.

What this request has to say about keeping its response: the page cache's entry, who may share it, and how the response revalidates.

Visitor options the server renders: theme, density, a dismissed banner.

A page on the site.

A RecordCollection of Page objects.

A File that is publicly visible and knows which page it belongs to.

Manages every file owned by a page/item/user - identified by owner UUID + filename - including its index, public mirror, and image variants.

A PageFile that is an image. transform() (and the src()/srcset() helpers built on it) only compute the target variant URL and record the requested options via Registry::setVariant() : no pixels are touched here.

A page whose children come from somewhere other than pages/ - an API, a database, a file.

Base for anything stored as an _index.json + _data.json folder (Page, User).

A lazy, immutable list of records.

SQLite index of every page UUID with its path, view, status and timestamps. find() queries it with the comma-separated DSL.

The current HTTP request: path segments, query, post body, uploaded files, and whether htmx sent it.

Holds the routes a view registers for its page, plus before and after hooks.

Session values and flash messages under one name, so views and addons can't overwrite each other's keys.

The visitor's session as `$app->session`: login, the signed-in user, permissions, CSRF and throttling.

A user account.