Reference

Routes

A route is a URL a module answers. A module's routes page lists each one with its path parameters and the variables its view receives, so you know what a template can use before you open it.

Three views, three addresses

Templates: URLs of the public site, such as /{fullSlug} for a page, and what their templates receive.
API & Jobs: REST endpoints, under /cdna-api/. Most modules document none here; the API Reference covers the REST API.
Admin: cdna-admin screens, under /cdna-admin/.

Each view of a module has its own address, for example /developer-docs/reference/routes/Pages/admin. The view you choose is remembered, and links to routes pages follow it.

Reading a route

A route shows its HTTP method, its full path and its name. Parts in braces, such as {id}, are path parameters, listed with the pattern they must match. Below that is what the view receives: each variable with its type, linked to the model page. Only GET routes list their variables.

Variables every template gets, such as $_request, $_url and $_currentSite, are not repeated on each route; see Global template variables and Core classes.

Public site

Modules whose pages your site renders, and what their templates receive.

Start with Pages Blogs Books Faq Products Users

Admin screens

cdna-admin screens you are most likely to customise, and what their templates receive.

Start with Pages Products Users Sites Hooks

Every module with documented routes is in the navigation of any routes page.

Objects ReferenceGenerated from the platform, so it is always current

API ReferenceEvery REST endpoint, in cURL, PHP, Python and JavaScript

Routes

Three views, three addresses

Reading a route

Public site

Admin screens