Website boilerplate

misaki-studio-website is a general Next.js shell for running a Misaki Studio frontend locally or serving its static export yourself.

Current status: early starter. The public repository is reachable, but its current main branch has no README, pins an older Misaki runtime, has no build script, and defines next start even though its Next config uses static export. Use it for evaluation only until you have reviewed and corrected that shell for your application.

Current public dependency snapshot

Verified from the public package.json on 2026-09-09:

• Dependency: misaki-studio-internal · Current public value: 0.1.52

• Dependency: next · Current public value: ^15.5.19

• Dependency: react / react-dom · Current public value: 18.2.0

• Dependency: sass · Current public value: 1.42.1

• Dependency: styled-components · Current public value: ^6.4.2

These values describe the current starter, not a promise that exported output supports only those versions. Revalidate compatibility before changing them.

Clone and install

git clone https://github.com/Misaki-Studio/misaki-studio-website.git
cd misaki-studio-website
npm install

Do not export yet. First commit the clean clone so the first generated-output diff is easy to inspect.

Configure the export target

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

In the project's settings/export file, add a LOCAL FOLDER config:

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

Both frontend directories must exist before local export. The current public clone already contains src/ and public/.

Ask an agent to prepare the target without writing:

Read my project's export settings and verify that this clone contains src and public. Propose a local-folder target using those exact absolute paths, leave the backend path empty, and stop before adding the target or exporting.

After approval, the agent can use add-export-target, read the target back with get-export, and run export-code-to-folder.

Run locally

After export:

npm run dev

The current script starts Next development on http://localhost:8810.

Verify the first load, every exported route, direct navigation to nested routes, responsive behavior, images/fonts/media, and the browser console. Then run a TypeScript check independently because the Next config ignores build-time TypeScript errors:

npx tsc --noEmit

Build and serve the static output

The public package currently has no build script. Its next.config.js sets output: "export", so a direct Next build writes a static out/ directory:

npx next build

Serve out/ with a static host. The repository includes an nginx.conf example. Do not rely on its current npm start command without reworking the configuration; next start is a server command, while this shell is configured to produce static files.

The current config also:

• uses trailing-slash routes;

• recognizes .tsx pages;

• enables styled-components compilation;

• disables React Strict Mode;

• ignores TypeScript build errors;

• inlines only its allowlisted public environment names when present.

Review each of those choices against your application rather than treating it as a generated-code requirement.

Generated and owned files

Treat src/ and exported assets under public/ as generator-owned unless your target policy narrows the boundary. Put hosting configuration, CI, deployment scripts, adapters, and handwritten application code outside directories the exporter rewrites.

Before every re-export, commit the clone and search the target for the exporter's HAND EDIT (not produced by the exporter) warning. After export, review the complete diff and run the local checks again.

Known limitations

• There is no public README or supported production checklist yet.

• The public starter lags the runtime version vendored with the current Misaki Studio source.

• ignoreBuildErrors: true can allow a static build to finish while type errors remain.

• The provided start script does not match the static-export architecture.

• This frontend-only configuration does not host the generated database backend.

Use Cloudflare or Vercel when you want a documented provider-specific static deployment.