jefmari/awesome-wysiwyg-editors

A curated list of awesome WYSIWYG Editors.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 26 minutes ago
Type:Curated List / Learning ResourceCategory(s):UI Components & Design SystemsWeb Development
Added to GitGenius on September 17th, 2026
Created on April 21st, 2017
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 257
Total Stargazers: 3,982 (+0)
Total Subscribers: 87 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.7 days
Mean response time: 26.5 days
90th percentile: 49.1 days
Tracked items: 4

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Awesome WYSIWYG Editors is a curated list that catalogs WYSIWYG editors and rich-text editing tools.

The project addresses the problem of discovering suitable WYSIWYG editors by organizing them into a comprehensive reference. It groups editors by their implementation approach: standalone editors that work without external dependencies, jQuery-based solutions, and framework-specific implementations for Angular, React, and Vue. The list also includes Ruby-based editors, WYSIWYG-alike tools, and icon resources. This categorization helps developers quickly identify editors that match their technology stack and architectural requirements.

Developers should use this list when evaluating which WYSIWYG editor to integrate into a project. It suits anyone building applications that need rich-text editing capabilities and wants to compare options across different frameworks and dependency models. The standalone category is particularly valuable for projects seeking editors without framework coupling, while the framework-specific sections help those already committed to particular technology stacks find compatible solutions.

The project's development activity is primarily driven by questions raised in the issue tracker, indicating that users engage with the repository mainly to seek clarification or guidance rather than to propose structural changes or additions.