​
Publishing Path

Scritorio’s first wedge is editorial development and coaching, but the long-term product should support the whole author journey from blank page to self-published book. This path is a core differentiator for indie authors. Scritorio should give them a local, author-controlled way to combine craft feedback, reader simulation, visual planning, metadata, ebook preparation, audio-version production, preflight checks, and export preparation. Authors pursuing traditional publishing can use the same development workflow, but self-publishing readiness should remain a first-class product requirement.

​
Long-Term Goal

An author should eventually be able to:
  1. Start a new project with little or no writing experience.
  2. Learn through coaching exercises.
  3. Develop an idea, argument, story, or book structure.
  4. Draft chapters or scenes.
  5. Use editorial review and reader feedback to revise.
  6. Prepare supporting visuals, notes, citations, indexes, and bibliography material.
  7. Lay out the final book.
  8. Export files suitable for self-publishing services such as IngramSpark.
  9. Produce ebook and narrated audio versions from the same reviewed manuscript source.
The author remains the writer. Scritorio supports the process, teaches craft, checks quality, and helps prepare production-ready outputs.

​
Publishing Scope

Publishing support should eventually include:
  • front matter and back matter management
  • chapter ordering and manuscript assembly
  • title, subtitle, series, author, imprint, ISBN, category, keyword, and description metadata
  • style and typography presets
  • print layout preparation
  • ebook export preparation
  • PDF export for print review
  • EPUB export for digital review
  • ebook package validation for metadata, navigation, front matter, back matter, links, images, and table of contents
  • narrated audio-version planning and production
  • narrator voice, character voice, and pronunciation management
  • cover and interior metadata tracking
  • cover art concepting and final-cover asset management
  • interior art, chapter art, and illustrated-book asset management
  • ISBN, trim size, bleed, margin, and imprint metadata fields
  • index, bibliography, footnote, and endnote production support
  • preflight checks for missing assets, broken links, unresolved comments, and incomplete metadata
  • self-publishing readiness reports that explain what still needs author attention before upload

​
EPUB And Ebook Publishing

Ebook support should be a first-class part of the publishing path, not a side effect of print layout. Authors should eventually be able to:
  • assemble the manuscript into an ebook-specific structure
  • generate EPUB files for review and distribution
  • manage ebook metadata, cover image requirements, table of contents, links, front matter, and back matter
  • preview likely reading order and navigation
  • run preflight checks for broken links, missing images, malformed headings, and incomplete metadata
  • keep EPUB generation reproducible from local Markdown, templates, and export profiles
Scritorio should treat ebook output as one of several publishing targets. The manuscript remains local Markdown; the EPUB is a generated artifact that can be recreated as the book changes.

​
Audio Versions And Narration

Scritorio should eventually support audio versions of written books. The goal is not only quick read-aloud review, but author-directed narrated production where the same manuscript can become an audio edition. Audio-version workflows should support:
  • a project-level narrator voice
  • per-character voice assignments for dialogue-heavy books
  • optional section, chapter, or viewpoint-specific voice rules
  • pronunciation dictionaries for names, invented terms, places, acronyms, and technical language
  • manuscript segmentation into narratable units such as chapters, scenes, dialogue runs, and correction takes
  • generation through audio providers such as ElevenLabs or other voice platforms
  • provider profiles for model choice, voice IDs, cost tracking, output formats, and usage limits
  • local storage of narration plans, voice casting notes, pronunciation notes, generated clips, and revision history
  • review workflows for listening, flagging mistakes, regenerating lines, and approving final takes
  • export assembly for chapter-level audio files and a complete audio package
The author should control voice casting, pronunciation, pacing direction, regeneration, and final approval. Generated audio should never become the canonical manuscript; it is a publishing artifact derived from the reviewed text and local narration plan.

​
Self-Publishing Targets

IngramSpark is an important example target for self-publishing readiness. Scritorio should not hardcode itself only to one vendor, but it should eventually support export profiles for services with concrete formatting requirements. Vendor profiles should help indie authors understand practical requirements without turning Scritorio into a closed publishing platform. Export profiles may include:
  • print-ready PDF requirements
  • EPUB requirements
  • audio package requirements
  • trim sizes
  • bleed and margin expectations
  • cover file requirements
  • metadata checklists
  • upload package checklists

​
Cover And Interior Assets

Self-publishing workflows should support both text production and visual production. Authors should eventually be able to manage:
  • cover concepts
  • front cover, spine, and back cover requirements
  • jacket or full-wrap cover metadata
  • chapter-opening images
  • interior illustrations
  • children’s book spreads
  • nonfiction figures and diagrams
  • asset status from concept to final
Scritorio should help brainstorm and evaluate these assets, but the author controls final choices. The system should preserve prompts, source context, imported references, generated variants, and production notes locally.

​
Relationship To Markdown

Markdown remains the manuscript source of truth. Publishing workflows should assemble, transform, and export from the local project without locking the author into Scritorio-only files. Publishing-specific files may include local configuration, templates, generated layouts, ebook artifacts, narration plans, generated audio clips, export logs, and preflight reports.

​
Relationship To Coaching

Publishing is not just a final button. Scritorio should help authors grow into the process. For new writers, coaching should support:
  • idea development
  • premise and argument formation
  • story structure or chapter structure
  • scene and section drafting
  • revision practice
  • reader awareness
  • final polish
The product should be able to meet authors at the beginning, not only after they already have a finished manuscript.

​
Early Boundaries

Publishing support should not displace the MVP. The early product should prove that Scritorio can open a local project, help the author write and revise, run useful reviews, and save reports locally. Final layout, vendor-specific export packages, and production-grade print workflows can come later, once the manuscript development loop is strong.