What this template is
A finished reference site you clone, then make your own.
Abstract illustration of a diagonal stack of blog entries
blog-template is a finished reference site. Clone it into a new app, then replace the copy, images, theme and config before launch.

This site is a template. Every page you can see — the home page, the blog, the privacy, terms and cookies pages — exists so that a new site can start from something finished instead of something empty.

How it is meant to be used

You do not edit this site. You clone it into a new app namespace, and then you change the copy, the images and the theme until nothing of the template is left. The clone is a straight copy of every content entry under this app, rewritten under the new app's name. Cross-references between entries are preserved, so the new site renders exactly like this one on the first build.

What to change before you launch

  • Copy — every page here is written to read as real content, not as filler. That is deliberate: it sets the quality bar. Replace it with your own.
  • Images — the illustrations are a small, coherent SVG set. Swap them for your own artwork and update the alt text.
  • Theme — colours, fonts and spacing come from a shared default. Your site overrides them in two small files. See Theming a cloned site.
  • Config — the site name, domain and analytics id live in one settings entry. Point them at your site.

Why a template at all

Standing up a site by hand means recreating the same page structure, the same navigation and the same policy pages every time, and getting some of it subtly wrong. Starting from a known-good copy means the structure is already correct and the only work left is the work that is actually yours: the content.