migrate01
All migration notes

From Scrivener · WriteIDE 0.6

Keep the Scrivener binder, or compile a copy WriteIDE can import.

WriteIDE is not a Scrivener clone and it does not open .scriv files. In 0.6 the honest paths are compile-then-import, or keep drafting in Scrivener and use WriteIDE as the point-in-time tracker for stats, items, skills, and quests.

now02

Shipped in 0.6

What WriteIDE does with that manuscript.

Story Overview showing cast, power curve, and story position for a tracked manuscript
  • Import a compiled copy

    Compile from Scrivener to Word, Markdown, or plain text. WriteIDE detects chapter and scene structure from headings and breaks, then lets you review the split.

    0.6
  • Keep Scrivener as the manuscript home

    Tracker-only is the 0.6 path for authors who want the binder, corkboard, or compile system they already know. WriteIDE sits beside it as the continuity ledger.

    0.6
  • Track progression Scrivener treats as text

    Levels, HP, inventory, classes, skill charges, and quests are database records tied to scenes, not numbers you retype in a status document.

    0.6
  • Stay local-first

    The WriteIDE project is a separate local folder. Compiling does not upload the Scrivener project, and WriteIDE does not need an account.

    0.6
limits03

Not in 0.6

What this path does not do.

  • Native .scriv import

    Binder order, status labels, keywords, snapshots, and custom metadata do not come across. Only the compiled manuscript text can be imported.

    Not in 0.6
  • Replacing Scrivener compile or corkboard

    WriteIDE has outline, board, and export tools of its own. It does not claim Scrivener compile depth, iOS, or a one-click binder takeover.

    Not in 0.6
  • Live sync with the Scrivener project

    A later compile is a new import or a manual update. There is no watcher on the .scriv package in 0.6.

    Not in 0.6
steps04

Local-first

How to do it on this computer.

  • 01 · Compile to .docx, Markdown, or .txt

    Include the chapter headings you want WriteIDE to treat as structure. Binder labels alone are not enough.

    01
  • 02 · Download WriteIDE 0.6

    Open the desktop app on the same computer that holds the compile.

    02
  • 03 · Import the compile or start tracker-only

    Import Manuscript if you want the prose in WriteIDE. Track a story written elsewhere if the binder stays canonical.

    03
  • 04 · Use Story Overview as the ledger

    Record changes at the chapter you have actually written. If headings were thin, accept the skeleton and backfill as you go.

    04