milkdown/milkdown

🍼 Plugin driven WYSIWYG markdown editor framework.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 5th, 2026
Created on March 9th, 2021
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 549
Total Stargazers: 11,896 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 39.8 hours
90th percentile: 0.0 hours
Tracked items: 212

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 12% of issues opened in the past year have been closed. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 341 days
Stale 30+ days: 22
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (142)
  • enhancement (59)
  • planned (2)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Milkdown is a plugin-driven WYSIWYG markdown editor framework built on TypeScript that lets developers embed a rich-text editor capable of rendering and editing markdown in web applications.

The tool addresses the need for a flexible, extensible markdown editor by combining ProseMirror as its underlying document model with a plugin architecture that allows customization at multiple levels. Rather than shipping as a monolithic editor, Milkdown provides a framework where features are implemented as plugins that can be selectively included, configured, or replaced. This approach means developers can build editors tailored to their specific requirements, whether that involves supporting GitHub Flavored Markdown, custom syntax extensions, or particular UI behaviors.

Teams should consider Milkdown when they need a markdown editor that can be deeply customized without forking the codebase. It suits projects where the editing experience must align closely with application-specific workflows or where markdown syntax support needs to extend beyond standard CommonMark. The plugin system makes it particularly valuable for applications that may evolve their editing requirements over time, since new capabilities can be added through plugins rather than requiring core changes. Projects that prioritize a WYSIWYG editing experience while maintaining markdown as the underlying format will find the framework's design philosophy aligned with their needs.

The project shows active development with regular commits addressing bug fixes, feature additions, and plugin ecosystem expansion. The codebase demonstrates ongoing refinement of the plugin API and integration patterns. Documentation and examples receive consistent updates to reflect framework capabilities and usage patterns. The maintainers actively engage with the plugin ecosystem, suggesting a commitment to the extensibility model as central to the project's direction.