Choosing a WYSIWYG Editor for Drupal
2
Tags :
I recently gave a talk at SANDCamp on how to set up a WYSIWYG editor, and after the session Graham asked me why my preference was for the TinyMCE editor over the CKedior, or any other. I figured I'd write up my preferences here, in case anyone was wondering the same thing.
My preference for TinyMCE is personal. I like it for several reasons: First, TinyMCE has a mature, thriving Open Source community of its own. Additionally, WordPress also includes the TinyMCE Editor, and we can't ignore the amount of work that community is putting into the development and improvement of TinyMCE as well. I expect faster progress of TinyMCE because lots of people are using it, and lots of developers are working on it.
Every time I've needed a plugin for something that wasn't already included (for example: a youtube button, spellchecking, or HTML templates) it's always already existed for the TinyMCE editor. And if you need to create a new plugin of your own, TinyMCE also has really great documentation, something our community might learn something from :)
The TinyMCE editor itself is also closely integrated with the WYSIWYG module. For example, there seem to be a lot more plugins for TinyMCE - than almost any other editor - already integrated.
Clients also often prefer using the TinyMCE editor. No WYSIWYG editor is going to make creating tables in your content easy, but I find it less painful with TinyMCE than with other editors.
One of my favorite modules for use with WYSIWYG is the caption filter module, and what that module does (allow you to float a caption right or left along with its image) is technically impossible using the CKEditor. Because of this last limitation, I suspect TinyMCE will be the editor that gets into Drupal 8 core.
At the end of the day, everyone should choose the editor that's best for them, their clients, and their needs. If you prefer the CKEditor, or another, then by all means, do what makes you happiest :)
Comments
Post a comment
Top Keywords
all
-
drupal82
-
best practices34
-
solving obvious problems23
-
howto21
-
design19
Presentations
- Upcoming
- Past
all
-
Beginner ThemingDavid Needham
-
Open Academy: A Higher Education Drupal Product For Departmental WebsitesMatt Cheney
-
EFF + Drupal + Civicrm = GreatElly Jonez
all
-
Usability Studies for you and Drupal too!Jennifer Lampton
-
Best Practices WYSIWYG with inline image handlingJennifer Lampton
-
Best Practices WYSIWYG with inline image handlingJennifer Lampton
What we've coded
all
-
On The WebJennifer Lampton
-
Conference Organizing DistributionMatt Cheney
-
Live UpdateJon Skulski
Videos
all
-
Taking Drupal Back!
Upcoming workshops
all
-
Drupal FundamentalsSan Francisco, CAFebruary 28, 2012enroll
-
Drupal Scalability and PerformanceDenver, COMarch 19, 2012enroll
I am so glad to get this comprehensive appraisal. CKEditor is not my preference. Can't wait to go with TinyMCE next time.
Thank you so much for taking the time to share this info.
Do you have any experience with the D7 version of the autosave module with TinyMCE and how stable it is even though it's a dev release? drupal.org/project/autosave
I'm really interested in the same auto-save functionality you get when creating and editing a Google Doc; basically there is no save button since the document is saved after 5 keystrokes and/or 3 seconds of inactivity (huge guess there).