Putting it online
A Verso site builds to plain files, so any static host can serve it. Connect the repository once, and every Publish after that updates the live site.
Your host watches your repository. When Publish pushes a new commit, the host installs your site's packages, runs the build and serves the result. You set this up once.
The two settings
Every host asks the same two questions:
| Setting | Value |
|---|---|
| Build command | npm run build |
| Output directory | dist |
Cloudflare Pages
- In the Cloudflare dashboard, go to Workers & Pages and create a Pages project from a git repository.
- Choose your site's repository and the
mainbranch. - Set the build command to
npm run buildand the output directory todist. Leave the framework preset as none. - Save and deploy.
Netlify
The starter includes a netlify.toml that already holds both settings:
[build]
command = "npm run build"
publish = "dist"
In Netlify, add a new site from your repository. It reads the file, so there's nothing to fill in.
What the host needs
- Your packages must be installable. The host runs
npm installfrom yourpackage.json, soverso-cmsandelevate-frameworkmust come from somewhere it can reach, like the public npm registry. A dependency that points at a file on your own computer will fail on the host. - Node.js 18.19 or later. Most hosts use a newer version by default. If yours doesn't, set the
NODE_VERSIONenvironment variable in the host's settings to20or later. - Nothing else. The build is pure JavaScript, image resizing included, so there are no native modules or system libraries to install.
At the top of a domain, or in a folder
Templates write every address from the root, like /journal/ and /elevate.css, which suits a domain or subdomain such as example.com or docs.example.com. To serve the site inside a folder, like example.com/site/, add "base": "/site" to verso.json. The build then puts /site in front of every address that starts at the root. See Feeds and sub-folders.
Extras the build can make
A few files are made only when you ask for them in verso.json or in content/:
| File | How to get it |
|---|---|
404.html | Make a page at content/404/. Cloudflare Pages and Netlify both show it for addresses that don't exist. |
sitemap.xml | Add "url": "https://example.com" to verso.json. |
feed.xml | One per channel, with "url" set and the folder listed in "channels". See Channels. |
pages.json | Add "index": true to verso.json. It lists every live page with its text, for search. |
{
"name": "Northlight",
"url": "https://northlight.studio",
"index": true
}
Draft pages are left out of all of them, and out of the built site.
After that
That's the whole loop: open the editor, change the page, press Publish, and the live site updates a minute or two later. The rest of these docs cover the editor in depth, then templates for building your own designs.