Prepare a project

Install the Kujo runtime using the official documentation and read the SSG repository requirements. Work from a local SSG checkout or an established project using its build entry point. Review its content, templates and configuration before changing them.

Kujo documentation ยท SSG source and requirements

Build and preview

From the SSG project directory, these verified commands generate static output and serve it locally. Replace the example domain with the intended canonical origin.

kujo run ./build.kujo -- --site-url https://your-domain.example
kujo serve output --port 8080

These commands build an SSG project. They do not crawl an existing website, copy its content or convert plugins.

Inspect the result

Open the local preview, follow navigation links and check assets and page metadata. Edit source content and templates, then rebuild; generated output is not the source of truth. SiteKit provides reusable interface foundations, but project-specific layouts and accessibility still need review.

Explore SiteKit

Prepare deployment separately

Publish only the intended static output. Keep credentials and private source data out of it. Verify the hosting provider's current limits and plan any forms, search or other services separately. A successful local build is the starting point for migration validation, not proof of a completed migration.