v0.16.0 (preview)

Push content in from your own system, and let a worker handle the narrating.

• A public content API (/api/content/v1) — a documented, versioned HTTP contract for connecting your own CMS or publishing system to StoryLark directly, without going through the admin portal or the CLI: push a single chapter, a whole book, or import a zip/batch of many books at once for onboarding a whole catalogue in one go
• A bulk narration queue — text pushed through the admin portal, the content API, or a bulk import is queued for narration and picked up by a worker you run wherever you already publish from, with real per-job progress and a time estimate once anything has completed
• Re-narration is per block, not per chapter — editing one paragraph re-synthesizes just that paragraph; the rest of a chapter's audio is reused unchanged, and costs nothing against a metered voice's character budget
• Reorder chapters from the admin portal, and a real safety net between it and the CLI: a publish or a portal save that would overwrite someone else's more recent edit is refused instead of silently applied

Found a gap? StoryLark is open source — improve these notes on GitHub.