It's been requested/discussed so many times in various issue queues. Drupal needs a WYSIWYG editor in core, since so many users consider it a key feature missing (either compared to what they are used from other CMSs or that's what they expect when they first instal Drupal). Most people are aware that there is a way to achieve this feature, but what they want is an 'official' out-of-the-box solution.
Even if this gets either 'wontfixed' or 'postponed' (like for ever), at least we'll have a place to point people to each time this question comes up elsewhere. This issue will serve as an answer to people wondering if it will ever happen - not how. So...
Note/plea: this is not a place to start flaming over which particular solution is best, but rather a discussion over if this should happen or not. Once that is decided, we'll see what we'll choose to go with (based on features, looks, well-maintenance, popular demand - I don't know). So please, for the love of God if you must, then head over here instead for such comments:
Status update - Latest news
This project is a branch of Drupal 8 whose purpose is to bundle a WYSIWYG editor into core. This project is a branch of Drupal core (rather than a branch of the existing WYSIWYG module) because the approach used in this sandbox integrates tightly into the Filtering system.
quicksketch also states:
The most central concept we need to develop is the idea of filtering not only output but on input as well...
- If you can help with coding, then head here: .
- If you want to be informed when something is available for testing (in drupal core 8.x-dev), then subscribe here: .
Decided to remove the contenteditable WYSIWYG bullet from Phase 2. It'd be a huge undertaking, not really an HTML5 issue, and one that should really be its own separate initiative.
This session is going to be a discussion more than a demo of proposed code. We'll take a look at what solutions other systems (namely WordPress) have included to deal with rich text editing, and we'll identify the central problems with building similar functionality into Drupal.
Ultimately, the solution currently being pursued will be an overhaul of the "Filter" module (which currently is only designed for filtering on output), and replacing it with a new module that controls not only filtering on output but also on input, making it possible to provided a true WYSIWYG (or at least a lot closer than anything we have today).