Deployment
htmlpress build produces a fully static site in
.htmlpress/build/: one .html file for every page at the same
path as its source, a 404.html, robots.txt, a
sitemap.xml (when site is set), a _headers file,
a _redirects file when a language has no home page of its own, the
Markdown copies and llms.txt
for agents, the theme and component scripts under _htmlpress/, and every
other file of the project. 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 htmlpress.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
htmlpress buildat the project root and the output lands in.htmlpress/build/. In CI,npx gethtmlpress buildruns the same binary without installing it first; see Introduction for the other channels. -
You've set
siteinhtmlpress.yamlif you wantsitemap.xml, the sitemap line inrobots.txt, canonical URLs and absolute social tags; see Site Metadata. -
You only need
baseif 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 Htmlpress