# From Claude Fable Demo to Live Website: The Missing Publishing Step > Turn a Claude Fable or AI-generated demo folder into a protected, trackable live Revdoku website with one shareable URL. AI tools can generate impressive interactive demos, explainers, and microsites, but teams still need a practical way to publish a Claude Fable demo or any AI demo to a live website. The operational question: where does the folder live, who can open it, and how do you keep the shareable URL after the next edit? This tutorial treats Revdoku as the missing interactive demo hosting step after generation. ![Generated website files in Revdoku](/assets/en/blog/fable-demo-to-live-website-publishing-step/01-generated-files-in-bucket.webp) Note: Revdoku works with ordinary generated files: a Claude Fable demo, microsite, or another AI-generated project. The source can come from Claude, Codex, ChatGPT, a local script, or another AI workflow. ## 1. Keep the generated AI demo folder intact When an AI tool produces a demo, preserve the folder structure: - index.html - CSS and JavaScript - images, audio, video, or generated media - JSON, CSV, or Markdown data - supporting assets and subfolders Do not flatten the folder unless the app requires it. Relative paths usually matter. ![Publish generated folder](/assets/en/blog/fable-demo-to-live-website-publishing-step/02-publish-generated-folder.webp) ## 2. Publish the AI demo to Revdoku Create or update a Revdoku bucket with the generated files. Publish it so the AI demo goes live. This gives the demo a shareable live URL without a separate deployment project. For demos, I prefer this order: 1. Publish privately. 2. Open the live URL. 3. Test desktop and mobile behavior. 4. Fix obvious layout or asset issues. 5. Share only after the review pass. ![Live generated demo](/assets/en/blog/fable-demo-to-live-website-publishing-step/03-live-generated-demo.webp) Note: test the live site like a real visitor sees it, not only in the AI tool preview. ## 3. Use password protection for early review If the demo contains early product messaging, client work, or unfinished UI, keep it password-protected during review. Revdoku enforces password access at the bucket publishing layer, not with a decorative popup inside the generated HTML. ![Protected demo review](/assets/en/blog/fable-demo-to-live-website-publishing-step/04-protected-demo-review.webp) ## 4. Keep the same shareable URL through later AI edits The biggest advantage is continuity: after feedback, update the same project folder and republish to the same Revdoku bucket. That gives you: - one review link, - one analytics history, - one access mode to manage, - one public URL when the demo is ready. ![Demo analytics](/assets/en/blog/fable-demo-to-live-website-publishing-step/05-demo-analytics.webp) Note: analytics show whether reviewers opened the demo and which paths they used. ## Takeaway AI generation creates the experience. Revdoku turns it into a protected, trackable, updatable URL. That publishing step turns a demo folder into a real website someone else can use. Start publishing for free Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish. Copy Prompt or Create Free Account ## Frequently asked questions ### Can I publish an AI-generated demo without rebuilding it? Yes. If the demo already includes an index.html file and its supporting assets, you can publish the generated folder as-is. The key is to keep the original file structure intact so relative paths continue to work. ### What types of AI demos can be published this way? This works for Claude Fable demos, microsites, explainers, prototypes, and other generated web projects. The source does not matter as long as the output is ordinary website files such as HTML, CSS, JavaScript, images, and data files. ### Why should I publish privately before sharing the demo? A private review step helps catch broken assets, layout issues, mobile problems, or unfinished messaging before others see the demo. It is especially useful for client work, early product concepts, or internal prototypes that are not ready for public access. ### How does password protection help during review? Password protection limits access at the publishing layer, so reviewers must authenticate before viewing the bucket. This is more reliable than adding a visual password screen inside the generated HTML because the restriction applies before the site content loads. ### Will the demo URL change after I make edits? Not if you update the same Revdoku bucket. You can revise the generated files, republish, and keep using the same review or public URL. This avoids sending new links after every round of feedback. ### What should I test after publishing the live demo? Open the live URL and test it the way a real visitor would. Check desktop and mobile layouts, navigation, media loading, interactive elements, and any paths that depend on assets or data files. ### Why are analytics useful for an AI demo? Analytics show whether reviewers actually opened the demo and which pages or paths they used. This can help confirm engagement, spot unexpected navigation behavior, and keep review history tied to one consistent URL. --- [View the canonical page](https://revdoku.com/blog/fable-demo-to-live-website-publishing-step/) · [Browse llms.txt](https://revdoku.com/llms.txt)