Skip to main content
For Lettercamp Cloud, use npx lettercamp check to verify compatibility before deploying. The standalone build below uses your local dependencies and writes files for another host. Run the build from your publication directory:
Replace https://example.com with your public site URL. The CLI uses its origin (scheme and hostname, plus port if present) for site metadata and its pathname as the site’s base path. The URL must use HTTP or HTTPS, without credentials, query parameters, or a fragment.

Host under a subfolder

Include the path in your site URL:
Serve the output at /blog/ on your host. Lettercamp prefixes publication links with that base path. Use full URLs for links to pages outside the publication.

Output and assets

By default, builds copy public/ into the output. For example, public/images/cover.jpg is served at /images/cover.jpg on a root-hosted site. Local preview also serves these files. The bundled starter’s images and fonts work with this default; you do not need a Cloud account or asset upload. Upload the entire output directory to your static host, including generated JavaScript and copied public files. Pages use directory-style URLs with trailing slashes, so your host must serve each directory’s index.html. Choose a different output directory:
Use a CDN for generated assets:
Upload the generated assets to that CDN location as part of your deployment. The asset prefix applies only to generated assets; it does not upload them or rewrite references to files copied from public/. Use --remote-assets-only to check a publication that already uses hosted asset URLs before GitHub publishing. This mode rejects local media and fonts, including design.typography.localFonts: true. CLI deployment prepares supported local images automatically before running these checks. The build writes static files for your hosting provider. It does not deploy them. Use a dedicated output directory: the build can replace its contents. The CLI rejects output paths that would replace your publication root, its ancestors, or overlap pages/, components/, or public/.