Static site publishing
Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.
Appaloft can publish build output from Vite, Astro, Next export, documentation sites, or plain HTML as a reachable URL. Start with Cloud browser upload, or use the CLI and self-hosted control plane when the site belongs on your own server.
npm run build
# Output is usually dist/, out/, or build/
# Cloud: choose static files in Appaloft and publish
# CLI: appaloft deploy ./dist --config appaloft.ymlAligned with
Cloud static artifact upload strategy, website quick upload copy, and public Appaloft static resource deployment path.
Run the project's build or export command to produce dist, out, or an equivalent static directory.
Small sites can start with Cloud upload; projects with an existing server can use the CLI or self-hosted control plane.
Open the published URL and check the homepage, deep links, images, CSS/JS, and error page.
Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.
Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.
Official Blueprints help users choose app templates, then hand deployment back to Cloud and related entrypoints.
Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.
Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.