Cloudflare boilerplate

misaki-studio-cloudflare builds a Misaki Studio frontend as a Next.js static export and deploys the resulting out/ directory as Cloudflare Workers assets in your own Cloudflare account.

It has no Worker application code. Cloudflare serves the exported files directly.

Requirements

• Node.js 20 or newer

• A Cloudflare account for deployment

• Cloudflare login through Wrangler, or scoped CI environment credentials

• A frontend-only Misaki Studio project, or a separate verified host for any generated database backend

The current public repository uses Next 16.3.3, React 19.2.8, and misaki-studio-internal 0.1.76. Treat these as a dated starter snapshot and review its current package.json before installation.

Clone and configure

git clone https://github.com/Misaki-Studio/misaki-studio-cloudflare.git
cd misaki-studio-cloudflare
npm install
cp .env.example .env

Set:

• SITE_NAME to the public site name;

• SITE_URL to the final origin without a trailing slash.

If SITE_URL is empty, the current SEO script still writes robots.txt but skips the sitemap and llms.txt instead of guessing an origin.

Export into the clone

Coverage: UI + MCP. Desktop required for local-folder export.

Configure a local target:

REACT SRC PATH → <clone>/src
ASSET PATH     → <clone>/public
NODEJS SRC PATH → empty

Commit the clean clone, export the whole project, then inspect the diff. src/, public/, and the exported SEO generator are generator-owned; wrangler.jsonc and next.config.js are boilerplate-owned shell configuration.

Build and verify locally

npm run build
npm run preview

The current scripts build the Next static export into out/ and serve it through Wrangler at http://localhost:8787.

Check every route, direct navigation, the generated 404 page, assets, responsive behavior, browser console, robots.txt, sitemap, and llms.txt. Then run the dry-run packaging check after a successful build:

npm run check

The dry run does not require deployment credentials.

Deploy

Deployment is an external action:

npx wrangler login
npm run deploy

For CI, use CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID in the environment. Do not put credentials in the command line, Markdown, export settings, committed .env, or agent prompt.

The default wrangler.jsonc serves out/ and uses the generated 404.html for unknown paths. Rename its Worker and review its compatibility date before the first deployment.

For a custom domain, configure a Workers custom-domain route, set SITE_URL to the same origin, rebuild, and verify the generated absolute URLs before deploying.

Ask an agent to prepare the deployment

Coverage: UI + MCP for export; provider CLI for deployment.

Inspect the Cloudflare clone, verify its Node requirement and scripts, and read my Misaki Studio export targets. Propose the src and public paths with no backend path. Do not install, export, log in, build, or deploy.

After approval, an agent can configure/export and run local checks. Wrangler login and deployment mutate your external Cloudflare account and require separate explicit approval.

Current limitation

This target is static-site only. A project with generated database views/actions will build a frontend whose backend calls have no service here. Do not deploy that project with this boilerplate until its backend has a separately supported host.