Small, complete projects for learning Spacefast, testing framework support, and moving an existing site without starting over.
Every directory is independent. Clone the repository, enter one example, and let the CLI detect the framework, install dependencies, build, and publish:
cd astro-with-wordpress npm install npm run dev # the framework's own dev server sf publish
Use sf build when you only want to prove the deployable artifact locally.
sf dev is the local server for Zero apps (zero/, kitchen-sink/); for
everything else, use the framework's dev server.
| Directory | What it proves |
|---|---|
jekyll/ |
Ruby/Bundler detection, Jekyll build, and _site output |
gatsby/ |
Gatsby detection and public output |
zero/ |
The smallest useful Spacefast Zero app |
blog-with-custom-templates/ |
Static publishing plus _layout.html, _pages, theme.json, and sf.jsonc |
nextjs-static/ |
A Next.js static export served entirely as files |
nextjs/ |
Server-rendered Next.js, route handlers, and automatic OpenNext packaging |
astro-with-wordpress/ |
Astro built from WordPress through @spacefast/wordpress |
functions-php/ |
Native PHP Functions with JSON, form bodies, validation, and verified auth context |
recipes/ |
Canonical prompts, metadata, live outputs, and the public recipe feed |
kitchen-sink/ |
Zero, Pages, PHP, JavaScript, TypeScript, auth, mail, and routing in one project |
migrate-from-cloudflare-pages/ |
Wrangler build settings and Pages convention files |
migrate-from-vercel/ |
vercel.json build, redirects, rewrites, headers, and cron import |
migrate-from-netlify/ |
A full Netlify project, including Functions, plugins, contexts, forms, and the explicit ports they require |
Each example README calls out the important files, the expected build output, and any product boundary that cannot be translated automatically.
recipes/ is the source of truth for spacefast.com/recipes.
Each recipe contains its copy-paste prompt, gallery metadata, runnable output,
and live URL. GitHub Actions compiles those records into the historical public
feed at https://spacefast.github.io/examples/manifest.json and publishes only
changed recipe outputs.
Do not duplicate recipe prompts in another package or repository. Framework examples teach an integration; recipes are user-facing starting points that an agent can customize and publish.
The pull-request workflow builds every top-level project through sf build,
runs the Zero app tests, validates every recipe output, and builds the recipe
manifest, without creating a live version. migrate-from-netlify builds its
prebuilt output, because sf build has no flag to accept the Netlify features
that still need a port.