Deployment

Woozie compiles to plain static files. You can host the output literally anywhere.

Build for production

woozie build

This creates a build/ folder:

build/
    index.html
    about.html
    contact.html
    styles.css
    app.js
    custom.js          -- only if you have a script.js

Where to deploy

Vercel

1. Push your project to GitHub
2. Import the repo at vercel.com
3. Build command: woozie build
4. Output directory: build
5. Hit deploy

For clean URLs (no .html in the address bar), add a vercel.json:

{
  "cleanUrls": true
}

Netlify

1. Push your project to GitHub
2. Import at netlify.com
3. Build command: woozie build
4. Publish directory: build
5. Deploy

For clean URLs, add a netlify.toml:

[[redirects]]
  from = "/*"
  to = "/index.html"
  status = 200

Or turn on "Pretty URLs" in the Netlify dashboard under Site settings > Build & deploy.

GitHub Pages

1. Run woozie build
2. Push the build/ folder to a gh-pages branch
3. Enable GitHub Pages in your repo settings

Anywhere else

Upload the build/ folder. It's just HTML, CSS, and JS. Any static host works — Cloudflare Pages, Surge, S3, your own server, whatever.

Clean URLs in production

The dev server handles clean URLs automatically (visiting /about serves about.html). In production, you need to configure your host to do the same. See the provider-specific instructions above.

Before you deploy

• Run woozie build and check the output
• Open the built files locally to make sure pages work
• Check that images and assets are in the project folder (they get copied to build)
• Make sure woozie.rules has the right title, theme, and font
• Add clean URL config for your hosting provider