With the core systems stable, I shifted focus to everything surrounding the platform. Talescape now has its first public-facing website. The site introduces the platform’s purpose, explains the roles of Bards and Dreamers, and outlines the roadmap for the next development stages. It is connected directly to the backend API, which allows documentation and dynamic content to be shared between the app and the website.

I also wrote the first version of the official documentation. It covers the main systems of the editor, including story creation, events, actions, conditions, and the media library. The documentation will grow with each update, but it already provides a clear overview for early users and internal testers. Integrating it with the API makes it possible to display help articles directly inside the editor later.

Outside the app, I began building the community infrastructure. Talescape now has a Discord server, which will serve as the main hub for announcements, development discussions, and contests. I also created the first social media accounts to reserve the official names and prepare for public communication.

These steps mark the beginning of Talescape’s transition from internal development to public presence. The technical foundation is in place, and the focus now shifts toward inviting the first Bards and gathering feedback before release.

I started preparing the marketplace system. The first goal is to define how stories will appear once they are published and how pricing, tags, and filters will work. Most of this work happens on the backend for now, setting up data structures for listings, images, and search integration. It will later connect directly to the publishing workflow so approved stories can move to the marketplace automatically.

At the same time, I continued refining the contest workflow. The first internal version already supports contest creation and submission marking, but the voting and result logic are still missing. These parts will be added later once the publishing and marketplace systems are stable.

For the next few weeks I will pause work on core systems to focus on creating promotional material. Talescape is nearing the stage where the first Bards will be invited for internal testing, and I need to prepare visuals, text, and documentation to present the platform clearly.

The first draft of the publication workflow is now complete. Stories can now move through defined release stages that cover the full process from draft to public release. Each story version, called a release, follows a clear sequence that ensures both technical and content quality before it becomes available to Dreamers.

A release begins as a draft, where all settings and content can be changed freely. Once ready, it moves to Ready for Review and runs through the automated validation process. The system checks for missing media, unreachable scenes, invalid variables, and incomplete metadata. If issues are found, the release automatically returns to draft status with a detailed report in the Checks tab.

When a story passes automated review, it proceeds to manual moderation. Moderators verify compliance with the content guidelines, accuracy of age ratings, and the correct use of AI disclosures. Once approved, the system packages and publishes the story to the marketplace. Each step is tracked in the release timeline so authors can see exactly where their story stands in the process.

Releases can later be updated through new versions, and older versions remain accessible to keep previously downloaded stories functional.

A starting point for a contest system was added around the same time, but it is still in development and not connected to the publishing flow yet.