Deploy guides
Step-by-step guides for putting a static site live on thin.host, one per framework. Each covers the build command, the folder to deploy, the base-path setting for the /s/<slug>/ preview URL, a prompt for your agent (Claude Code, Cursor, ChatGPT and other MCP clients), the equivalent curl call, and the custom-domain step.
| Guide | Build | Deploy this folder |
|---|---|---|
| Astro | npm run build |
dist/ |
| Vite (React) | npm run build |
dist/ |
| Vue | npm run build |
dist/ |
| SvelteKit | npm run build |
build/ |
| Next.js (static export) | npm run build |
out/ |
| Nuxt (generate) | npx nuxt generate |
.output/public/ |
| Gatsby | npm run build |
public/ |
| Hugo | hugo --cleanDestinationDir --minify |
public/ |
| Jekyll | JEKYLL_ENV=production bundle exec jekyll build |
_site/ |
| Eleventy (11ty) | npx @11ty/eleventy |
_site/ |
| MkDocs | mkdocs build |
site/ |
| VitePress | npm run docs:build |
docs/.vitepress/dist/ |
| Docusaurus | npm run build |
build/ |
| Plain HTML | none | the folder with index.html |
| An HTML page from a Claude or ChatGPT chat | none | the folder with index.html |
The same three steps for every framework
- Build static files with the base path set for where the site will be read:
/s/<slug>/for the thin.host preview URL,/for a custom domain. - Deploy the output folder: ask your agent to publish it through the thin.host MCP server, or zip it and
POSTit to/v1/websites/archive. - Map a domain from the dashboard (CNAME to
cname.thin.host, automatic TLS), then rebuild with base/.
New to the MCP server? Start with Quickstart (MCP). Moving from another host? See thin.host compared.