Livemark
LivemarkMarkdown site generator

Deployment

Updated May 16, 2026

livemark build produces a fully static site in .livemark/build/client/ — index.html files for every route, plus sitemap.xml, robots.txt, RSS feeds (when configured), and your assets. Drop that directory on any static host and you're live.

These guides walk through the most common targets. Pick one — every guide is self-contained and shows both the manual command and a CI workflow.

Hosts

Static Hosting

Any host that serves a directory of files — nginx, S3 + CloudFront, Caddy, and friends.

GitHub Pages

Free, git-native, and works well for project sites under a /repo-name/ path.

Cloudflare

Workers + static assets. The setup livemark.dev itself uses.

Vercel

Git-connected with previews per pull request and zero-config domains.

Netlify

Git-connected with branch deploys, atomic releases, and built-in form handling.

What every guide assumes

  • You run livemark build and the output lands in .livemark/build/client/.
  • You've set site in livemark.config.ts if you want sitemap, robots.txt, and RSS to generate with absolute URLs — see Site Metadata.
  • You only need base if your site is mounted at a sub-path (e.g. GitHub Pages project sites). The GitHub Pages guide is the only one that covers it.

Created with ❤ and Livemark