Demo data
How content is stored in this demonstration, and how it maps to a production setup.
Storage status
In production
- Content API. Stories, chapters and genres move to a database behind authenticated endpoints; the Studio calls those endpoints instead of browser storage.
- Server-rendered pages. Story and chapter pages are rendered on the server (or statically generated) with per-story titles, descriptions and structured data for search engines.
- Editor accounts. Roles for owners, editors and authors, with an audit trail replacing the local activity log.
- Reader accounts. Saved stories, progress and history sync across devices.