Skip to content

meldoc.io › Roadmap

Roadmap

What we’re working on now, what’s coming next, and what’s planned later.

Looking for recent updates? Check the changelog →

In Progress

Quality & Audit

  • Stale content detection: the documentation review on pull requests already catches what a change makes untrue, and after the merge marks it on the document itself. Next is the rest: documents that fell behind the code outside of any pull request — found on a schedule, so a page nobody has touched still gets checked

Coming Next

Editor & Content

  • Callout blocks: highlight important information with styled NOTE, TIP, WARNING, and CAUTION blocks, so a warning reads as one instead of as another paragraph
  • Sub-pages widget: automatically show child documents inside a parent page — easy navigation through hierarchical docs
  • Workspace-level templates: share document types across every project, with a starter library — ADR, runbook, API reference, post-mortem, RFC, changelog — so a new project does not start by redefining the same types
  • Manage templates through your AI assistant (MCP): create and edit document templates over MCP, so splitting an existing project into document types does not mean dozens of manual dialogs

Search

  • Smarter search in the web app: jump to the exact section, get one-click AI summaries, navigate with keyboard — so a search ends on the answer rather than on the page that contains it

Import / Export

  • Export to PDF and DOCX: download an individual document or a whole project, not just the workspace-wide Markdown archive available today — for the reader who needs a file, not a link
  • Import from Confluence: bring your existing Confluence spaces into Meldoc, alongside the Notion and Markdown import that already ships

Integrations

  • Bitbucket connection: the server-side sync and the pull-request checks for Bitbucket, as GitHub and GitLab have them — so a Bitbucket repository no longer needs the CLI in a pipeline

Future Plans

Collaboration

  • Document ownership: assign a responsible owner to each document, so a page has somebody whose job it is to keep it true — they get notified when linked code changes
  • Notifications: an in-app notification centre and email for comment mentions and replies — today a mention waits on your Start page — so a question left on a page reaches the person it was meant for wherever they are

Knowledge & Discovery

  • Workspace AI chat in the web app: ask questions, get answers from your documentation, save responses as new documents
  • Automatic cross-project sync: when docs in one project change, dependent projects can update automatically instead of somebody remembering to copy the change
  • Contradiction detection: extend the audit suite — which already covers duplicates, broken links, retired aliases, and unanswered questions — with documents that contradict each other, so two answers to one question are found before a reader finds them

Enablement

  • Parallel doc versions: keep v1 and v2 of the same documentation side by side for APIs and SDKs, with a version switcher for readers. This is separate from version history, which already records how a single document changed over time

Integrations

  • Slack bot: ask questions and get answers from your documentation directly in Slack, with change notifications for subscribed channels — so the answer arrives where the question was asked

Quality

  • Verified documents: a verified state with an expiry, surfaced as a signal in search and audit rather than a workflow gate, so a reader can tell a page somebody has checked from one nobody has

Enterprise Readiness

  • Google & Microsoft SSO: sign in with Google or Microsoft accounts, so joining a workspace does not mean another password
  • Custom limits & configurations: for workspaces a plan tier does not fit
  • Enterprise support workflows: for organisations that need an agreed path when something goes wrong
  • Compliance / security requirements: the controls and paperwork a procurement review asks for