# Editor handbook

The optional editor writes Markdown on your own server. markstack.app is documentation only; it has no public writing service. Set up your own instance through Optional editor before following browser-writing tasks here.

# Open and edit an authorized page

Screen and writing controls explains the file tree, source, preview and toolbar. Use the account intended for your role. An administrator can reach more content than a section writer, so administrator tests do not prove writer restrictions.

Choose the exact source path, read its metadata and make a small synthetic change. Preview helps during writing but is not the final built reader. Save and reopen to verify server source before asking for publication.

# Preserve unsaved work

Drafts and recovery explains browser-local drafts, navigation warnings and access/session recovery. A draft lives in that browser, not automatically on the server or another device. Preserve it before clearing browser data or repairing sign-in.

Coordinate concurrent writing. The editor does not have a general realtime merge/page-version service; two writers can otherwise overwrite saved work. Compare current server text before applying a recovered draft.

# Manage paths deliberately

File actions covers create, rename and delete. Confirm the exact target and link/draft consequences. A folder rename changes source paths; title metadata changes public routes. They are different operations.

Deletion has no built-in undo. Source history/backups and removal of deployed old files belong to the surrounding workflow. Do not delete a source folder merely to hide it from navigation.

# Hand saved work to publication

Section writers save authorized content and ask an administrator to publish. Administrators review all intended saved changes before starting the shared publisher. Other writers’ saved pages can enter the same build; unsaved tabs cannot.

Save, publish and deploy separates source save, local output, Git and hosting. Verify the generated reader and actual remote deployment. No browser button silently substitutes for your chosen source-review or deployment process.

# Complete a writing task

Check the intended account/path, source/preview, saved text, draft state and reader result. When access changes, sign in again and retest allowed/denied paths. When a build or host fails, preserve correct source while fixing that layer rather than retyping the page.