Storybook runs as a separate Vite process so component work doesn't pollute the app's dev server. Two ways in:
Requires the Storybook dev server to be running. Start it with:
npm run storybook
Generate a static export and serve it from a sibling path. After deploy, Storybook is reachable at /storybook/.
npm run build-storybook # outputs to storybook-static/
Then drop the build behind a static-file proxy in your deploy target — Netlify, Vercel, Cloudflare Pages all support this with a one-line redirect rule.
More stories will land as components are extracted from EventProptech.tsx per the code-review refactor plan (see docs/CODE_REVIEW.md).