Your first site
A Verso site is a folder of plain files. Templates hold the design, content holds the words, and the folder path is the address.
The starter is a small studio site called Northlight, with a home page, an about page, a journal with two posts, a Topics page for the journal's tags and a page for missing addresses. Its header and footer carry your site's name. It's there to edit, take apart and replace. Here's what's in the folder.
The folders
| Folder or file | What it holds |
|---|---|
templates/ | The page types: page (a header, a block area and a footer) and post. Plain HTML with Elevate classes and fields. |
templates/page.layout.json | The starting layout for new pages of the page type. |
parts/ | HTML that templates share. It starts empty. See Parts. |
blocks/ | The sections editors add, move and nest on a page: a header and footer, a hero, text, features, a team, a quote, the latest posts, a list of tags and more. |
content/ | The pages. Each folder with a page.json is one page. |
content/site.json | What's the same on every page: the shared header and footer. |
public/ | Files copied into the built site as they are, like the favicon. |
elevate/ | Elevate's setup. Your colours, fonts and sizes live in elevate/design/tokens.json, which the Design panel edits. elevate/design/site.ts is for extra tokens written by hand. |
verso.json | The site's name, its locale, the classes rich text gets, search, and the journal channel. |
A page is a folder
The path of a folder in content/ is the page's address. content/ itself is the home page, content/about/ is /about/, and content/journal/the-first-week/ is /journal/the-first-week/.
Inside each folder, page.json names the template and holds the page's settings and its plain fields:
{
"template": "post",
"title": "What we do in the first week",
"description": "Before we draw anything, we spend five days listening.",
"date": "2026-10-02",
"tags": ["Process", "Research"],
"fields": {
"heading": "What we do in the first week, before we draw anything.",
"cover": { "file": "cover.jpg", "alt": "An orange sun rising behind a long table." }
}
}
Rich text fields each get their own file beside it, named after the field: a field called body is kept in body.html, as clean HTML with no classes. Images the page uses sit in the same folder, so they move with it.
A template is HTML with fields
Open templates/post.html. It's an ordinary HTML page. Where a value goes, the template names a field:
<h1 class="font:instrument:h1:regular:tight">{{ heading:text }}</h1>
<img src="{{ cover:image }}" class="block w:full h:auto">
<div>{{ body:rich:headings:lists:links:images:tables:quotes:callouts:embeds }}</div>
Each field is written as name:type:modifiers. The name is how page.json stores it. The type says what it holds: a line of text, rich text, an image, a color, or a block area for blocks. Modifiers like required or a rich field's tools come last. Fields covers them all.
templates/page.html is shorter. Between a shared header and footer, it has one block area, {{ content:blocks }}, where every section of the page is a block. See Blocks and block areas.
There's no list of fields to keep anywhere else. Type a new field into a template and it exists. Every page using that template can fill it in.
Make a page by hand
You'll usually make pages in the editor, but it helps to do it once by hand. Make a folder and a page.json:
mkdir content/hello
{
"template": "post",
"title": "Hello",
"fields": {
"heading": "Hello from a file"
}
}
Save it, and /hello/ exists. If the editor is running, it notices the new folder straight away. It also reloads the page you're looking at whenever a template, block, stylesheet setting or content file changes, so you can keep the editor open while you work in your code editor.
Styles
Every class in a template is an Elevate class, built from your design tokens. Verso compiles them as you edit and again when you build. A class Elevate doesn't recognise stops the build and names the file and line, so a typo never reaches the live site. See Elevate in Verso for more.
Next: edit a page in the browser.