> For the complete documentation index, see [llms.txt](https://docs.storychain.ai/storychain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storychain.ai/storychain/community-engagement-system/how-to/ready-to-go-web-ui.md). # Ready to go Web UI {% embed url="" %} *With StoryChain, every project gets its own ready-to-go Web UI for their community!* Your users can explore all the generations and even create brand-new stories—right from the Web UI. The best part? You can launch your custom Web UI in just a few seconds, complete with your own branding and theme! Simply head to **Settings**, then open the **Web UI** section. Enable the Web Interface, and your project page will be live and accessible in no time. From here, you can personalize everything—add your **branding description**, choose your **brand colors**, and fine-tune the look and feel to match your vibe. Make it yours! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.storychain.ai/storychain/community-engagement-system/how-to/ready-to-go-web-ui.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.