42 Flagship Stories: The Launch Catalog

Photo: Unsplash

Launching a new platform with empty content is a bad idea. Anyone who arrives at OutaStory for the first time and finds empty shelves clicks away — and probably doesn't come back. That's no secret, but the consequence is work: you need content before the community is big enough to fill it itself.

We took this task seriously. At launch, OutaStory has 42 flagship stories — 21 in English, 21 in German.

Why 42, and why 21 each?

The number isn't a coincidence. We have 21 root categories in the new hierarchy. And we decided that every root category gets at least one long, complete story. One per genre, two languages — that adds up to 42.

But the number is also a minimum statement: every one of these stories is long. Not a few hundred words. Every flagship story has eleven chapters, each chapter three to four reading pages. That's roughly 13,000 to 15,000 words per story.

Add it up: 21 English stories come to around 290,000 words. 21 German stories around 280,000 words. Together that's almost 570,000 words of original content at launch.

What "flagship" means

Not every story on OutaStory is a flagship story. We also have around 750 shorter seed stories, mainly meant for testing search and category navigation.

Flagship stories are positioned differently. They are:

• Long enough to fill multiple reading sessions
• Self-contained narratives — no cliffhanger at the end of the last chapter without a resolution following
• Representative of their genre — anyone looking for fantasy should find a story in the fantasy flagship that takes the genre seriously
• Bilingual — the German and English versions are not translations of each other, but independent stories within the same genre

The last point matters: the German "Dunkle Fantasie" story doesn't take place in the same world as the English "Dark Fantasy" story. Each language gets its own worlds, its own characters, its own plotlines.

Why eleven chapters?

The chapter structure was a deliberate decision. Chapters that are too short don't allow for depth. Chapters that are too long scare people off the first time they open a story.

Eleven chapters at three to four pages per chapter produces a story that feels like a complete narrative — with an introduction, turning points, and a resolution — without being so long that it feels like a novel you'll never finish.

For the audio system, the chapter structure has a technical reason too: each chapter is generated as its own MP3. Shorter units mean shorter generation times and easier resubmission if a chapter needs to be regenerated.

Photo: Unsplash

An overview of the genres

Each of the 21 root categories got its story. Some examples from the German catalog:

• Fantasy: An epic adventure in a world where magic is bound to language
• Romantasy: A love story between a blacksmith and an enchanted prince
• Science Fiction: A space station whose AI starts acting on its own after a system failure
• Dystopia: A society where dreams are monitored and traded
• Urban Fantasy: A detective in Berlin solving cases that are anything but normal cases
• Horror: A cabin in the woods, a closed group, a secret that's been waiting for them for a long time
• Fan Fiction: (anime setting, original world) A group of students who accidentally end up in a parallel world that runs on manga rules

The English catalog covers the same genres, but with its own worlds and styles — more American storytelling tradition there, more European here.

The seed system behind it

Technically, all 42 flagship stories live in YAMLs under SeedData/stories/. Each folder has a number: 801–821 for English, 901–921 for German. The YAMLs contain metadata (title, slug, author, genre, description, cover prompt for the AI), and the actual chapter text sits next to it as separate markdown files.

The Initialization.Data system reads these folders at startup, computes a hash of the content, and compares it against the stored hash in the database. Only if something has changed does it upsert. That means: if we fix a story, it's automatically updated on the next deploy, without touching the database manually.

This architecture has another advantage: when we want to add new flagship stories, we just create a new folder and define a new YAML. On the next deployment, the story is live.

The authors behind the stories

The flagship stories have fictional author profiles — separate German and English voices, each with its own slug, biography, and follower counts. These profiles aren't dummy data, but carefully thought-out personas meant to show the diversity of the platform.

The author system is tightly linked with Auth0: every author slug can be linked to a real Auth0 account. For the seed authors, that happens via the Initialization.Account system, which creates Auth0 users and stores the user ID pointer in Azure Key Vault.

What's next?

Next week: how AI-generated covers work — from idea to prompt to finished image — and how we integrated the process into the three-step publish wizard.