RhoMD Docs Download

Roadmap

Rho's planned next steps — sorted by timeline + priority. See Changelog for history / released versions.

⚠️ This roadmap is intent, not commitment — priorities / timelines may shift based on community feedback and resources.

Short-term (next 3 months)

v0.7 — Media embeds + improvements

Estimated: 2026 Q3

  • ✨ Audio / video embed — :::media directive embeds local / remote media
    • Pair with slider for scrubber
    • Cross-namespace sync between multiple media
  • ✨ Image gallery / carousel — multi-image browsing
  • 🐛 Hydration performance improvements
  • 🐛 mini DSL error messages improved readability

Rho desktop app v1.0 binary release

Estimated: 2026 Q3

  • 🎯 macOS / Windows / Linux binaries
  • 🎯 Auto-update mechanism
  • 🎯 File association (double-click .md to open in Rho)
  • 🎯 Personal use free / commercial deployment requires license

cloud.rho.md MVP

Estimated: 2026 Q3

  • 🎯 Online editor (write left, render right)
  • 🎯 Share URL (short link)
  • 🎯 OG preview auto-generation (Puppeteer)
  • 🎯 30 demo seed pool
  • See internal Cloud Roadmap

Mid-term (4-9 months)

v0.8 — Accessibility

Estimated: 2026 Q4

  • ♿ ARIA tags complete (all DSLs)
  • ♿ Keyboard navigation full support
  • ♿ Screen reader optimization
  • ♿ Color contrast auto-validation
  • ♿ Focus management (modal / tabs / stepper)

v0.9 — Performance

Estimated: 2026 Q4

  • ⚡ Lazy hydration as default
  • ⚡ Tree-shaking optimization (smaller bundle when using subset of capabilities)
  • ⚡ Pre-rendered fallback HTML (faster first paint)
  • ⚡ Vega-lite chart lazy load
  • ⚡ SVG render diff (animation only updates changed parts)

Rho graph early version

Estimated: 2027 Q1

  • 🌐 Cross-.md-file STG knowledge graph
  • 🌐 Auto-establish anchor → anchor links
  • 🌐 Visualize the overall knowledge network
  • 🌐 Search across all docs

Long-term (v1.0 and beyond)

v1.0 — Stable API

Estimated: 2027 Q2

  • 🔒 Strict SemVer commitment
  • 🔒 Conformance test pack release (other reader implementations can validate compatibility)
  • 🔒 Recommended baseline for commercial production
  • 🔒 v0.x → v1.0 migration guide
  • 🔒 LTS (long-term support) window commitment

v1.x — Ecosystem expansion

  • 🌍 Official framework adapters (React / Vue / Svelte / Solid wrapper components)
  • 🌍 CDN UMD bundle (use directly via <script>, no npm needed)
  • 🌍 CLI tool — rho format / rho lint / rho convert
  • 🌍 VS Code extension (syntax highlighting + preview + linting)
  • 🌍 Obsidian plugin (community or official implementation)

Rho AI

Estimated: 2027 Q2-Q3

  • 🤖 cloud.rho.md integrated LLM directly generates interactive docs
  • 🤖 Developer interface: Rho.aiGenerate(prompt) → markdown
  • 🤖 Fine-tuned model improves output quality
  • 🤖 See Rho AI / LLM Guide

Multi-language support

Estimated: 2027 Q4

  • 🌐 docs site adds ja / fr / de / es / etc.
  • 🌐 LLM Protocol translation full coverage
  • 🌐 Community-driven translation platform

Exploration / research

Maybe / not necessarily directions:

Database query capability

Similar: Notion database / Obsidian dataview. Form: :::query directive aggregates data across multiple .mds. Risk: increases complexity, crosses plain-text fallback boundary. Decision point: wait for community demand + finding a graceful fallback approach.

Collaborative cursors (cloud only)

Similar: Figma multiplayer. Cloud only — won't enter spec / @rho/md (keep stand-alone reader simple).

Embedding external HTML / Vue / React components

Reserved stance: violates plain-text fallback principle. Won't do unless strong use case.

Rho format standardization proposal

Long-term: may propose to W3C / CommonMark group to standardize parts of Rho. Needs evidence of strong ecosystem adoption first.

Won't do directions

Explicitly out of scope:

  • ❌ JS scripting in markdown (violates declarative principle)
  • ❌ Arbitrary HTML embed (violates plain-text fallback)
  • ❌ AOT compile to binary (breaks markdown's nature)
  • ❌ Cross-page persistent state (out of markdown's scope)
  • ❌ 3D rendering (use WebGL / Three.js / specialized tools)

How to influence the roadmap

We listen seriously to community feedback:

  1. GitHub Issue: file feature requests at scos-lab/markview/issues
    • Tag enhancement / idea
    • Describe use case + existing workaround / pain
  2. Discussion: discuss / vote on GitHub Issues
  3. Direct email (commercial customers prioritized): [email protected]
  4. PR: contribute directly → see Community

Resources / priorities

scos-lab is a small team — roadmap priorities depend on:

  1. Real user pain points (bugs / high-frequency requests)
  2. Commercial customer needs (paying customers get priority support)
  3. Spec consistency (avoid fragmentation)
  4. Community contribution willingness (PRs welcome)

See also