How-to
Website
Pre-render a page for each item
A page on a :param route, such as /posts/:slug, has no single file a static build can write. List the values in paths:, and the build writes one HTML file for each. This blog writes one file per post in posts.json:
Needs: "build": { "ssg": true } in webfluent.app.json (and meta.site_url, for the sitemap), and src/posts.json, a list of posts with a slug, a title, a date and a body.
type Post { slug: String, title: String, date: String, body: String }
data posts: [Post] = "posts.json"
page PostPage(path: "/posts/:slug", slug: String, title: "{posts.find(p => p.slug == slug)?.title ?? slug} — Blog", description: "A post.", paths: posts.map(p => p.slug)) {
derived post = posts.find(p => p.slug == slug)
head { meta(property: "og:title", content: post?.title ?? "Post") }
if let p = post {
Heading(p.title).h1
Markdown(p.body)
} else {
Alert("No such post").warning
}
}
How it works
For a post whose slug is hello, the build writes posts/hello/index.html, with that post painted and listed in the sitemap.
paths:must be known at build time: adatafile, aconstor a literal list.- Each value is seeded as the parameter (and as
params.slug), painted, and listed in the sitemap. - For a route with several parameters, each value is a map that names them:
paths: pairs.map(x => { year: x.y, slug: x.s }). title:anddescription:may name the page's parameters —title: "{slug} — Blog"— and each file gets its own. A title may also look the entry up, as this one does. Tags beyond the title and description go inhead { }(Add tags for one page).- A value that is not in
paths:has no file, so a static host answers with404.html(Show your own page for an unknown address). - A single-page build does not need
paths:at all: the router draws the page for any value in the browser.
Static or single-page says what else the build can paint into each file.