Voting starts in March for the Drupal Association Board election.
We need this to work on both the front end (inline editing) and backend (full node form).
From Wim Leers in #4:
I've been working on a solid comparison of the WYSIWYG editors that meet Spark's WYSIWYG goal.
Those goal is:
What we want to achieve is that previewing content through some sort of action is no longer necessary, because you're editing the content while it has its eventual styling, in the exact context where it will be used. In other words: the exact same CSS is used as the one that will be used when regular visitors view the site! You’d be able to just click on the node body and start typing, with some box-shadow-ish indication to make it clear that you’re editing the body, plus a formatting toolbar above the node body (which might follow along as you type). This is what we call “true WYSIWYG”. We can define it as a WYSIWYG that matches all CSS selectors identically like the eventual document would.
For all information, see the Spark: WYSIWYG editors evaluation Google Doc. We'd like you all to give feedback and update the Google Doc!
We're very much looking forward to your feedback! :)
Seefor a related discussion.