Format
iepub organizes interactive works around a manifest, story files, assets, and runtime resources that can be reasoned about independently. The goal is simple: the work should remain legible to humans and stable across reader, writer, and export steps.
Practical payoff
A format with visible boundaries makes it easier to audit content, debug reader issues, package a work, or evolve a project over time. That is especially useful once the book includes multiple languages, custom assets, or reader-side tools. Decadence already demonstrates those benefits in a public route.
Story files, assets, and runtime configuration are easier to inspect than one opaque bundle.
The same work can be served in the web reader, packaged, or validated without reinventing the model.
Related routes
Understand how the reader layer consumes the format.
Authoring Interactive fiction writerSee how Variant turns structure into an author workflow.
Example work Read DecadenceInspect a public book where the format is already carrying story and assets.
Library Open the libraryBrowse the public reader entry point and published works.