Export & desktop

Current desktop build: v0.1.0. Design stays in the browser; the app on your computer finishes local export.

#Browser versus desktop

Both surfaces open the same .ked.json book. There are three runtimes:

• Hosted web — write, design, save .ked.json, print to PDF, raster a cover PNG in the tab. DOCX offers a handoff to the desktop app instead of writing Word in the browser.
• Local web (this project on your machine) — the same editor, plus native PDF and DOCX through local export APIs.
• Desktop — the same editor, plus native PDF, DOCX, and cover PNG written as files on disk.

#Export formats

• PDF — print-faithful pages. Hosted web: Save as PDF from print. Local web and desktop: a file on disk. Export uses the pages currently on the canvas — finish typing before you export.
• DOCX — further editing in Word-compatible apps. Local web and desktop write the file. On the hosted site, a dialog explains how to continue on desktop.
• Cover PNG — raster of the composed cover for listings and shares. In the book editor the button appears when the cover page is selected. Hosted web rasters in the tab; desktop writes a file.
• Export KEd file — always a .ked.json download on a computer. That is the book package you import later.

#Installers

Same KEd Studio on macOS and Windows. Linux is not listed yet. Download the installer for your OS, then Import a saved .ked.json or continue a book already on that machine.

• m

  macOS

  .dmg installer

  Coming soon
• W

  Windows

  NSIS setup (.exe)

  Coming soon

#Handoff

Some flows open the web editor with a ?handoff= payload so a desktop session or a Kifuliiru generator can continue in the browser. The desktop app also understands kedstudio: deep links. Studio treats that as the incoming book and will not replace it with an older local draft. After it lands, save a file if you want a copy outside this browser.

The reverse path — hosted web asking for Word — opens a short dialog that points you at the desktop installer and a saved .ked.json.