Pages

Every .php and .md file in pages/ is a route.

Files and folders starting with _ are skipped, so helpers can live next to the pages that use them. When two routes could match, the one with fewer params wins, so pages/blog/archive.php beats pages/blog/[slug].php.

Templates#

A PHP page is a template. It gets the site as $site, the request as $context and the route's params as $params:

<?php // pages/blog/[slug].php ?>
<?php $this->layout("layout", ["title" => $params["slug"]]) ?>

<h1><?= e($params["slug"]) ?></h1>

$context is Dumbo's context, so $context->req->query("page") and the rest of the request are there. Escape anything you print with e().

A file extension in the name sets the content type. pages/feed.json.php is sent as JSON, and pages/rss.xml.php as XML.

Markdown pages#

A Markdown page renders in the view named by its layout front matter:

---
layout: page
description: Who we are.
---

# About

We make websites.

The view gets the rendered page as $page, with its html, title, meta (the front matter) and toc, and the page's meta tags as $seo. Without a layout, the page is the bare HTML. Content covers Markdown in more depth.

Pages with data#

A PHP page that starts with return defines its route with a Page. That's how a page lists the params to build, handles forms, or renders on every request. Page data covers each one.

Error pages#

pages/404.php renders for any route that doesn't exist, and builds write it to 404.html, which most static hosts serve for missing pages.

pages/500.php renders when a page throws in production, with the exception as $error. In development you get the error and the code around it.