With accounts in place, the next step is story structure. Talescape stories can now be organized into chapters and scenes, establishing a data model that can expand without breaking older projects. In parallel, the media system is rebuilt: instead of user-owned uploads, files now belong to a story, making collaboration and reuse inside a project far cleaner. The first rough editor interface is functional - bare bones, but already able to create and arrange stories directly in the browser.

This update covers the unglamorous foundation work: building the backend API and user system first, then choosing a login approach that stays secure without adding heavy support overhead. Talescape now relies on OAuth providers like Google, Twitch, Steam, and Discord, intentionally skipping classic email registration to reduce spam and maintenance. With authentication stable, the focus shifts to defining story structures in the database before the editor UI grows.

At the start, Talescape was just a need: a place to turn written ideas into interactive stories without fighting the tools. After bouncing between engines and rewrites, the project moves to the web to stay flexible, iterate fast, and aim for true cross-platform publishing later (Steam, mobile, maybe more). It reflects on two decades of development work, and why that background makes a long, interconnected system feel achievable.