Changelog

Markdawn is in public beta. This changelog tracks the product updates that make the same pages more useful for people, terminals, and AI assistants.

  1. The workspace gets its own home

    • The browser app now has a dedicated space for signing in, creating pages, and collaborating with a workspace.
    • The transition from learning about Markdawn to using it is clearer: when you are ready to work, go straight to the workspace.
  2. Hosted documentation for the whole workflow

    • The new documentation site brings the first steps into one place: create a page, import notes, organize folders, and share access.
    • When you are ready to go deeper, the same site covers the CLI, API, AI assistant workflows, and self-hosting.
  3. More reliable Obsidian imports

    • Notes with empty tag metadata can now be imported without treating an empty field as an error.
    • This keeps migration focused on the content instead of requiring frontmatter cleanup first.
  4. Better feedback from the CLI

    • Doctor and whoami now show resolved configuration and token access, making it easier to understand the environment before a command runs.
    • Commands, imports, exports, updates, and installers report progress and structured outcomes more clearly for both people and scripts.
  5. Manage pages and folders from the terminal

    • The CLI now handles the content lifecycle from a terminal: create, inspect, move, remove, restore, import, and export pages and folders.
    • Explicit confirmations, failure reporting, and machine-readable output make those operations usable by both people and scripts.
    • Because the CLI and browser share a workspace model, teams can switch interfaces without maintaining a second copy.
  6. Safer workflows for agents

    • Agents can make targeted content changes with preconditions and idempotency instead of relying on blind writes.
    • Diagnostics and skill workflows expose access, configuration, and supported operations before an agent changes content.
    • When a write outcome is uncertain, the workflow avoids automatic retries that could duplicate a change.
  7. The Markdawn CLI arrives

    • The standalone CLI gives people and agents a terminal interface to the same pages they use in the browser.
    • Authenticated workflows, safe content editing, shell completion, and platform installers make the first terminal session practical.
  8. Links become part of the writing flow

    • Typed and pasted URLs now become links without interrupting the editor workflow.
    • Link handling respects code, formatting, and document boundaries instead of changing content that should remain plain text.
  9. Keep important pages close at hand

    • Favorite pages and folders now appear alongside the rest of the workspace on the home dashboard.
    • Favorites keep frequently used knowledge within reach while preserving the existing access and collaboration controls.
  10. Share pages and folders with clear permissions

    • Pages and folders can now be shared with View, Edit, and Admin roles, so collaborators get the access they need without a complicated permission model.
    • Real-time permission changes keep active sessions aligned as access changes.
    • When access is lost or a collaboration connection becomes stale, read-only behavior protects the document from unsafe edits.
  11. A clearer path to self-hosting

    • Deployment checks and health reporting now make rollouts easier to verify before the application is restarted.
    • The deployment documentation includes a migration guide for moving a Markdawn deployment between servers.
  12. A more capable markdown editor

    • Properties support drag-and-drop ordering, inline editing, autocomplete, tags, and richer values.
    • Keyboard shortcuts and slash commands make common editor actions faster to discover and repeat.
    • Tables support insertion, keyboard navigation, and CSV or TSV paste.
    • markdown exports now preserve more formatting and can bundle referenced images as local assets.
  13. Connected pages and visible collaboration

    • Wiki links can suggest pages as you write, resolve to stable targets, and update backlinks when documents change.
    • Collaborative cursors, user avatars, and connection status make it clear who is working in a page with you.
  14. The first Markdawn workspace

    • The first working product brought together authentication, a browser editor, page persistence, workspace navigation, and collaboration.
    • Import and export workflows, workspace management, member invites, search, and a deployable application established the foundation for what followed.