Keep your Markdown together.

Use a workspace for a project, a course, or your own notes. Within it, organize documents in folders instead of keeping a long list of unrelated drafts. Your content stays Markdown, so you can download a file and continue working on it outside EDTR.md.

A small documentation workspace might look like this:

Product notes/
  README.md
  decisions/
    search-shortcuts.md
  releases/
    october.md

Choose names that describe the subject. Keep revisions in the same document rather than adding a new file for every edit.

Sign in to connect your workspace to cloud storage. When you are online, changes sync to your account. On another device, sign in to the same account and open that workspace.

Local editing and cloud sync serve different jobs. A document stored only in your browser is not automatically available on another computer. An offline change also needs an internet connection before it can reach your other devices. Before switching devices, let the current document finish syncing.

Start with a meeting notes template, or build a technical documentation workspace. Write in source, split preview, or the live editor as the task requires.

When a document is ready for readers, publishing creates a public copy. Publishing requires a paid workspace owner plan. Keeping the writing workflow separate from publishing lets you revise a draft before updating what readers see.

An authorized MCP client can read and update files in workspaces it can access. Specify the workspace and exact file path when asking it to revise an existing document. Your workspace role still applies: a viewer cannot use AI tools to write a file.

See Connect AI for setup and the same-file editing guide for a worked example. Use version history to review saved earlier text. Cloud storage is subject to the account’s storage allowance; see the current plans before choosing a workspace for larger files.