A practical static foundation.
What if rebuilding was the easy part?
The hard work is often deciding what should survive. List the pages, templates, content workflows, and runtime features you need before choosing a generator. Preserve useful design decisions, then test the new system against them.
Migrate WordPress without starting the design over
Inventory public URLs, licensed assets, canonical tags, redirects, and integrations. Separate rendered content from plugin behavior. Agree on form handling and search before export. Compare mobile layouts and representative templates; never silently remove application features.
What actually needs a CMS?
A publishing workflow may need an editor, preview, permissions, and scheduling. Static delivery does not remove those needs. Kujo SSG can generate a static frontend while a separately scoped CMS manages content. Frequent personalized responses still need a running service.
PHP runtime vs static delivery
A PHP application executes at request time; static files can be generated earlier. Reducing runtime components changes the operational surface, but does not eliminate dependency updates, access control, account security, or maintenance. Verify any exposed PHP version with your hosting provider, including backported patches.
Start with verified Kujo commands
Install the runtime using the official documentation, then read the SSG repository requirements. From a local SSG checkout, the verified build entry point is:
kujo run ./build.kujo -- --site-url https://your-domain.example
kujo serve output --port 8080These commands build an SSG project. They do not crawl or migrate an existing website.
Kujo documentation · SSG source and requirements · SiteKit
Verify the result, not just the build
Check internal links, assets, URL redirects, canonical and social metadata, keyboard access, reduced motion, mobile layouts, and visual differences. Validate forms against their actual destination with the owner’s permission. Record the artifacts and the unresolved differences.
Cloudflare Pages vs traditional PHP hosting
Static hosting can remove a per-request application runtime from delivery. Builds, forms, search, email, storage, and your time still have costs. Choose a provider after measuring requirements and checking its current quotas; free hosting is not universal.