Roadmap & Ideas Discussion

[mgks]

This thread is a living roadmap and a dump zone for all future-facing thoughts around docmd.

Some are real features, some are throwaway ideas - just so we don’t forget we had them in the first place. If they make sense, they’ll land in the pipeline and might be added to future releases.

We’ll cross out the ones that are implemented or ruled out.

Suggestions, feedback, experiments - all welcome.

✨ We are building the fastest, smartest docs system

🏛️ Implemented (Legacy Versions)

• Code Highlighting
• Containers
  • Callouts
  • Cards
  • Tabs
  • Steps
  • Changelogs
• Plugins
  • SEO
  • Sitemap
  • Analytics

🚀 0.3.x

• Live Preview (docmd Live)
• Plugins
  • Search
  • Mermaid.js

🚀 0.4.x

• Emoji Support
• SPA (0.4.8)
• SPA Lightning + Cache (0ms latency) (0.4.11)
• Plugins
  • LLMs (0.4.6)

🚀 0.5.x

• Documentation Versioning (0.5.0)
• Zero/Auto Config (0.5.0)
• Custom 404 (0.5.0)
• Simpler Config Instructions (0.5.0)
• Menubar (0.5.2)
• Plugins
  • Search Chunks (0.5.1)
  • PWA (0.5.1)
  • SEO V2 (0.5.1)
  • Themes V2 (0.5.3)
  • Plugin Installer (0.5.4)

🚀 0.6.x

• TS/ESM Migration (0.6.1)
• Navigation Architecture V2 (0.6.2)
• Breadcrumbs (0.6.2)
• Containers
  • Grids (0.6.4)
  • URL Embeds (0.6.5)
  • Hero Sections (0.6.7)
• Plugins
  • Analytics V2 (Auto-event tagging) (0.6.2)
  • Threads (Inline discussion threads) (0.6.8)
  • Math/LaTeX (0.6.9)

🚀 0.7.x

• Internationalisation (i18n) (0.7.0)
• Search V2 (Localised indexing & version tagging) (0.7.0)
• Zero-Config V2 (Auto trigger, bypass -z flag) (0.7.0)
• Advanced Plugin API & Live Sync (0.7.1)
• Auto-Deploy (Docker, NGINX, and Caddy) (0.7.2)
• Migrator V2 (0.7.3)
• Search V2.1 (Filter tags) (0.7.4)
• i18n V2 (Manifest + Better failsafe + Optimisation) (0.7.5)
• URL normalisation engine (0.7.6)
• Multi-Project Orchestrator (0.7.7)
• Containers
  • Tags (Badges) (0.7.4)
• Plugins
  • Mermaid V2 (0.7.3)
  • SEO V3 (0.7.6)
  • Git Integration (0.7.8)
  • OpenAPI (0.7.9)

⚡️ 0.8.x

• Multi-threaded WorkerPool Engine + Index Caching V1 (0.8.0)
• Pluggable Engine Architecture (Rust V1 - Preview) (0.8.2)
• Workspaces (Multi-Project V2) (0.8.3)
• Deployer (Auto-Deploy V2 - Github Pages, Vercel, and Netlify) (0.8.4)
• Search V3 (Offline Semantic Search Engine - docmd search) (0.8.5)
• Native MCP Server (0.8.6)
• Zero Config V3 (0.8.6)
• Docker Image (0.8.6)
• Agentic Skills (SKILL.md) (0.8.6)
• GitHub Action for docmd (- uses: docmd-io/deploy@v1.1 - Marketplace) (0.8.7)
• GitHub Repo Template (docmd-template) (0.8.7)
• Themes V3 (Dynamic Layout Engine) (0.8.7)
• Templates
  • Summer Preview (Modern minimal UI with feel good theme) (0.8.7)
• Plugins
  • OKF (Open Knowledge Format) Integration (0.8.8)
    • Knowledge Graph Test
  • Auth (Protected Docs)

⌛ 0.9.x

• memoryblock Integration
• Templates Marketplace
• MDXLite Integration
• Tooltips
• Focus Mode
• Plugins
  • LLMs V2 (AI Hooks / AI Integration Layer)
  • Document Exporter
  • Iconify Icons
• Containers
  • Playground (Interactive Live Codeblocks)
• Marketplace / Extensions
  • GitHub Actions / Apps
  • VS Code Extension
  • AWS Marketplace
  • Netlify / Vercel Extensions

⌛ 1.x.x

...

🎯 In Pipeline

• Analyse Mode (Docs Insights)
• Docs Auto-link
• Containers
  • ...
• Plugins
  • Health Checker (Broken Links, SEO, Missing Sections etc.)
  • Search V4 (Analytics + Insights)
  • Feedback
  • ...
    ...

🤔 Undecided

• Unified Publishing System (docs + blog + changelog)

[mgks]

I would genuinely love to invite you all to join the discussion. 🙏🏼

Along with docmd, we have come a long way. From day one, the promise was simple: keep the core minimal, zero config, instant setup, no heavy frameworks, no unnecessary layers.

That promise is still intact. It’s fast, lean, and intentionally small.

If you believe documentation tooling should stay simple and powerful at the same time, come build this with us. Suggestions, ideas, tough questions, and contributions are all welcome.

We also maintain a curated roadmap of features we believe belong in docmd. We’d love to add your suggestions for what should shape future releases.

---

@tonidy @yuciferr @cdervis @replicant026 @zcraber @tpalacino @jinam @mrexox @bbbonnibel @heiko-braun @daeho-ro @brisingr-eldest @ruturajpatki @jiuyuehe @AbdullahCXD @vassudanagunta @jschaufuss @amxv

[zcraber]

Would love to see a plugin for PDF generation.

[mgks]

Well, I'm not so sure about that for priority but maybe we put it in the undecided list for now.

[glassjaw]

My team has lots of workflows where timestamps are critical info across systems and we utilize PDF generation from existing markdown documentation with time stamps.

The ability to time stamp each item in steps containers with a simple click and seamlessly export to PDF would be a game changer!

[zcraber]

For icons, can I suggest using iconify instead of Lucide by default? It has over 200 icon sets with 275k icons including the Lucide. So, users will not be limited just by Lucide icons.

[replicant026]

A (probably dumb) question: instead the plugin/natively import the full package, isnt a way to connect to iconify and only download the svgs used when using build ?

[zcraber]

Maybe unplugin-icons, which is powered by iconify, can help with that. I'm not sure though.
https://iconify.design/docs/usage/svg/unplugin/#unplugin-icons

[mgks]

I'm thrilled to share that i18n is now fully supported! 🎉

We just launched docmd 0.7.0, which brings a massive architectural upgrade to the engine: Native Internationalisation (i18n) & UI String Translations.

You now have complete control over all built-in interface components, navigation elements, search placeholders, and even core plugins like Threads. The engine now resolves all UI text through JSON locale files.

How to use it:
Even if your documentation isn't natively multilingual, you can override the default text for branding purposes. Just define an en.json file (or your default language) in your assets/i18n/ directory and map the internal keys to whatever labels you want:

{
  "search.placeholder": "Search My Custom Docs...",
  "theme.dark": "Night Mode",
  "nav.docs": "Platform Guides"
}

If you ever do decide to expand into multilingual docs, everything lives right alongside it (/zh/, /hi/, etc.) safely isolated in their own localized route configurations, handled by true zero-config defaults.

Feel free to check out the i18n documentation to see the massive update we've pushed for this.

[replicant026]

thanks! You are really actively maintaining and improving docmd! I'm happy for you and for how docmd is evolving and developing, congratulations, truly, I wish more people would recognize it and start using it! Unfortunately, due to lack of time, I'm still stuck on version 0.2, but when I have time I will update it.

[mgks]

@replicant026 Thanks a lot, really appreciate that. 🙂

No worries at all, 0.2.0 was a long time ago now, so whenever you do get the time to update, I think you’ll find things a lot smoother and much feature rich. And if you run into anything during the upgrade, feel free to drop a discussion thread or open an issue.

[ruturajpatki]

Hello Gazi, This is a great news! Thanks for keeping docmd actively updated!! :-) I am also a big fan of your SmartWebView Android App template. I think you've stopped working on that project; but I still believe that project has a great deal of potential. Also, I think docmd deserves a Windows Desktop App wrapper. This way, it will be very useful for many. I can develop Flutter Desktop or .Net Desktop app wrapper around docmd if you like. Let me know and we can explore the opportunity in this area.

[robotgoat]

I've noticed that the current search plugin (0.7.2) searches across all versions of the documentation. As projects grow and major breaking changes happen across versions, would it be possible to change the search behavior so that it works across only the current selected version? Or if global version search is needed, it could be enabled by a search filter button in the search window?

The docmd engine keeps getting better and better! I love it over docusaurus.

[mgks]

@robotgoat

Just added search filter feature in release 0.7.4 based on versions listed, no config is required, enabled by default.

[mgks]

Just shipped 0.7.8: Focused on speed, visibility, and developer experience. And introducing a new core plugin git to show on page last edit timestamps, commit history and file edit anchor, all customisable.

Git Plugin (Core)

New built-in plugin that reads your Git history for last-updated timestamps, commit history tooltips, and edit-on-GitHub links, all zero-config.

plugins: {
  git: { repo: 'https://github.com/your-org/docs', branch: 'main' }
}

Faster Builds - Parallel Processing Engine

The build pipeline now uses batched parallel I/O (64-file reads, 128-file writes via Promise.all). For sites with 1,000+ pages, expect up to ~45-60% faster builds compared to 0.7.7.

Unified Terminal Interface

Consistency: build, dev, and multi-project - now shows the same high-signal output. No more silent waits. Live progress bars, cumulative page counts across all locales and versions, and per-project timing, in every build.

Auto-Install for Official Plugins

Reference any official @docmd/plugin-* in your config, if it's not installed, docmd downloads it automatically on build.

Container Syntax Compatibility

Migrating from VitePress or Docusaurus? Your :::tip, :::warning, :::note, and :::details containers now render out of the box with zero changes.

Full release notes: 0.7.8 Release Notes

Upgrade: npm install @docmd/core@latest

[mgks]

Hello everyone!

🚀 docmd v0.7.9 is released, which brings one of our most important features to establish better communication between LLMs and documents as-well help well define API level understanding in general - Native OpenAPI Rendering.

You can now embed beautiful, static API references directly in your Markdown without any client-side JavaScript or third-party dependencies like Swagger UI or Redoc. Everything is rendered at build-time into accessible HTML tables.

OpenAPI Usage Example

Simply point to your spec file (JSON or YAML) using the openapi code fence:

# API Reference

```openapi
assets/openapi.json
```

What else is new?

• Git Plugin Stability: Improved handling of commit history and edit links across all locales.
• TUI Polish: The terminal output is now more stable with aligned status indicators ([ WAIT ], [ DONE ]) for a cleaner build experience.
• Performance: Enhanced asset propagation for core plugins, ensuring zero-config deployments work out of the box.

Check out the updated OpenAPI Documentation for the full configuration reference.

I'm personally most excited about the 0.8.0 release and I'm sure you all will love it.

[mgks]

docmd 0.8.5 released

This release introduces semantic search as an alpha preview, adds automatic robots.txt generation, improves configuration migration, and fixes several rendering and development workflow issues.

• Semantic Search (Alpha): Added local embedding-powered semantic search through docmd-search, enabling context-aware search, typo tolerance, and related content discovery without external APIs.
• SEO Plugin: Added automatic robots.txt generation with sitemap support, AI crawler controls, and safe handling of existing files.
• Config Upgrades: Added docmd migrate --upgrade to automatically modernise legacy configuration files while preserving existing values.
• Mermaid Fixes: Fixed C4Context diagrams rendering as blank white boxes.
• Developer Experience: Added targeted rebuilds for configuration changes, automatic browser opening on startup, search result controls, and various UI improvements.

Semantic Search: https://github.com/docmd-io/docmd-search
Full release note: https://github.com/docmd-io/docmd/releases/tag/0.8.5
Discussion: https://github.com/orgs/docmd-io/discussions/9#discussioncomment-17139527

[mgks]

docmd 0.8.6 released

This release establishes docmd as an AI-First documentation engine with a native MCP server, modular agent skills, official Docker support, and a wide set of UI, search, and stability improvements.

Skills for docmd: https://github.com/docmd-io/docmd-skills
Complete release note: https://github.com/docmd-io/docmd/releases/tag/0.8.6
Discussion: https://github.com/orgs/docmd-io/discussions/9#discussioncomment-17192050

[mgks]

To make docmd accessible wherever developers and AI agents work, we are expanding the docmd ecosystem across multiple platforms and integration surfaces.

Whether you prefer local tooling, containers, GitHub-native workflows, reusable project templates, or AI-powered automation, docmd provides a consistent experience across the entire documentation lifecycle.

These integrations are still in their early stages and will continue to evolve over time. Features, capabilities, and developer experience will improve gradually as adoption grows and community feedback helps shape the ecosystem.

Native MCP Server

docmd mcp

This starts the MCP server over stdio. No network ports are opened, all communication happens through standard input/output streams.

Documentation: https://docs.docmd.io/api/mcp-server/

Official Docker Image

docker run -p 3000:3000 ghcr.io/docmd-io/docmd:latest

Package: https://github.com/orgs/docmd-io/packages/container/package/docmd
Documentation: https://docs.docmd.io/deployment/docker/

Agentic Skills

A modular skill set for AI agents to understand and work with docmd projects.

Repo: https://github.com/docmd-io/docmd-skills

GitHub Action for docmd

Zero config, with automatic project configuration detection.

Marketplace: https://github.com/marketplace/actions/build-and-deploy-documentation-with-docmd
Repo: https://github.com/docmd-io/deploy

GitHub Repo Template

Get docmd pre-configured and ready to deploy.

Generate: https://github.com/docmd-io/docmd-template/generate
Repo: https://github.com/docmd-io/docmd-template

[NellowTCS]

I've noticed the same issue across the partial templates. It slipped through before the release and will be fixed in the next version.

The spacing in the copy buttons was intentional to make it feel like a single control with two distinct actions, although you're absolutely free to customise it however you like. I actually really like what you've done with it.

Maybe combining them together like this then?

[NellowTCS]

That said, we can certainly continue expanding support for trusted component-based embeds, similar to what is already available through the ::: embed container.

Okay no worries!

[mgks]

@NellowTCS your new button UI looks really nice and about ::: embed containers, if you have any suggestions or services you'll like to be added or maybe want a custom embed you can suggest - https://github.com/mgks/embed-lite#supported-platforms

[mgks]

@NellowTCS we now have a complete custom template API in 0.8.7: https://docs.docmd.io/theming/templates/

You can now go beyond simple CSS customisation and build an entirely custom layout around your brand, product, or design requirements.

I've also built a preview template called summer, which you can try today from a source build. It will be published separately and installable through the same plugin system in a future release.

The template is primarily intended as a reference implementation for building your own. It doesn't reuse components from the default template, and custom CSS can be added on top as well.

I will try to experiment with some unique template designs also.

[NellowTCS]

This looks amazing!!!