Static by default
How to publish a Storybook site
A built Storybook is a static site, which makes this the cheapest way to give a designer or a client a component library they can click through.
- Build command
- npm run build-storybook
- Folder to upload
- storybook-static
Free plan, free SSL, no credit card.
-
Build the project
Run npm run build-storybook in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build.
-
Find the output folder
The build writes a finished site to storybook-static. That folder, not the project folder, is what gets uploaded.
-
Drag it in
Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL.
Worth knowing about Storybook
The script is
build-storybook, notbuild. Running the project build gives you the application, not the component explorer.The output folder is
storybook-static.It is a published web page, so it is public unless you protect it. Password protection is checked at the edge and covers every file, which is usually what an internal component library wants.
A story that calls a real API still calls it from the visitor browser. A published Storybook pointed at a staging service is a public pointer to that service.
Did an AI tool build this project?
Hosting an AI-generated website covers the question that comes before the build command: whether what you are holding is a single file or a project, and which of the two every tool actually hands back.