With core systems stable, Talescape expands beyond the editor into its public presence. A first website introduces the platform’s purpose, explains Bards and Dreamers, and outlines the roadmap, while also connecting to the backend API so content can be shared across app and web. Initial documentation now covers key editor systems: events, actions, conditions, media, and story creation, and is designed to later surface directly inside the tool. Community infrastructure begins too: a Discord hub and reserved social channels for future announcements.

This entry lays groundwork for the marketplace: how stories will appear to readers, how pricing and tiers might work, and which tags and filters will drive discovery. Much of the work is backend-first: data structures for listings, images, and search integration that will later connect directly to the publishing workflow. It also notes ongoing contest workflow improvements, while acknowledging missing pieces like voting logic. With internal systems stabilizing, the focus shifts briefly toward promotional material and clearer public-facing documentation.

The first draft of Talescape’s publishing workflow is complete, mapping how stories move from draft to public release. Each release progresses through defined stages, starting with free editing, then automated validation that checks media, scene reachability, variables, and metadata. Failures return the release to draft with a clear report; passing releases proceed into manual moderation for guidelines, age ratings, and AI disclosures. Once approved, stories are packaged for the marketplace, with a timeline that makes status and history transparent.