Import, share, and back up

Goal

Place external material in the right Space and choose an output suitable for delivery or backup.

Before importing

Confirm the target Space and prepare an Inbox for temporary material. Check for matching document or folder names to avoid confusion.

Import material

Choose an import method from the Space menu:

• Markdown file: import one .md or .mdx file.
• Directory: preserve the relative hierarchy of multiple documents.
• URL: extract a web page into a document.
• Drag and drop: add files from the system file manager.

After importing, check titles, hierarchy, body text, links, and images. Dynamic regions, signed-in content, and complex web layouts may need manual cleanup.

Chat can create a summary after you confirm that the source content is complete.

Export

Choose from the document menu:

• Markdown for continued editing or migration.
• PDF for a fixed reading layout.
• ZIP for the current document, child documents, and related resources.
• Copied Markdown or a local path for email, issues, pull requests, or developer tools.

For a browser-readable URL, use Publish a Cloud Page.

Backup and version history

Because a Space is a normal folder, you can back it up with Time Machine, a sync drive, an external drive, or Git. Keep important projects on your computer and in at least one other location.

Git is useful for long-lived text projects. .duobox/ and .downcity/ contain local runtime state and normally should not be committed. To move a Space to another computer, copy the complete folder and open it again.

Completion check

• Imported hierarchy, text, and images are complete.
• The exported file opens in its target reader.
• The backup contains the complete Space, not only one Markdown file.

Common issues

• Web content is incomplete: check whether the page requires sign-in or dynamic loading.
• A ZIP misses content: confirm that the documents belong to the exported subtree.
• Images disappear after moving computers: migrate the complete Space folder.