Deployment

MikroSlides ships as static files and can be served from any static host.

Download

curl -sSL -o mikroslides.zip https://releases.mikrosuite.com/mikroslides_latest.zip
unzip mikroslides.zip -d mikroslides

Deploy the extracted app files:

• index.html
• assets/main.js
• assets/styles.css
• copied static assets

Build From Source

npm install
npm run build

The production app is written to dist/.

Serve Locally

Serve dist/ with a static server. For a quick local check:

npx http-server dist -a 127.0.0.1 -p 8000 -c-1

Open http://127.0.0.1:8000.

Serving Online

You can serve the app from dist/ using any static hosting provider or static file server:

• Cloudflare Pages
• Netlify
• Vercel
• nginx, Caddy, Apache, or another static file server

Cloudflare

The repository includes wrangler.toml configured for Cloudflare static assets.

npm run deploy:cloudflare

The deploy command runs the full verification suite before publishing.

Storage Origin

MikroSlides does not need a database, auth service, API token, or server-side session. Browser storage is scoped to the deployed origin, so decks created on one host do not automatically appear on another host.

If you move between hosts or browser profiles, export a deck file and import it on the new origin.