We have been Beta testing a new WYSIWYG editor for forums for approximately 3 weeks now with a set of more than 20 sites. The feedback has been tremendously helpful, and the response to the new editor has been tremendous. We're very happy to unveil the new WYSIWYG for everyone as of this morning.
The new WYSIWYG editor makes creating, managing and editing forum posts much easier. Table support, embed support, item hover support and emoticon support have all seen significant improvements. In addition, the ability to see your edits provides a simplified set of feedback to the layout of your resulting post.
Why did you add a WYSIWYG?
WYSIWYG editing for forums and online content is becoming more and more standard. In addition, more and more people are using websites that don't want to learn esoteric formatting languages. They understand basic editors and can use them very well.
When I hit Enter I get two lines! What gives?
In the old editor there was no differentiation between paragraphs and line breaks. In a WYSIWYG editor they both exist. Enter adds a new paragraph, which has some padding after it. Leading to an extra line. Shift+Enter will add just a line break and the lines will be right next to each other.
This behavior is the industry standard for editors that have both paragraphs and line breaks.
What major benefits does a WYSIWYG have?
For the vast majority of users, especially novice users (of which there are more and more every day), the ability to easily see their formatting, image sizes, heading options, etc. gives them more confidence in what they are posting. The styling is directly visible. WYSIWYGs are meant to be a very close approximation to what you will see on the screen. With as much custom styling as we support this won't always be the case, but
This is a Heading
is easier to digest in the WYSIWYG than [ heading3]This is a heading[ /heading] for most people.
Why did you make it the default?
We had to pick one and we feel that the WYSIWYG has many long term benefits.
I Found a Bug! Where do I report it?
With this large of a change we expect a few bugs. We will work diligently to squash them. Please post them here or send them to firstname.lastname@example.org.
Can I disable the WYSIWYG?
You can. However, if you are seeing a bug or minor formatting issue please let us know so we can fix it instead of just turning it off. We've added an option in Admin -> Features -> Forums -> Settings that will allow you to disable the WYSIWYG site wide on your site. The default state is "ON", but for those of you who feel that you have no need for a WYSIWYG this will allow you to go back to that option site wide.
Do you plan to disable the BBCode Editor?
We have no plan to disable the BBCode functionality. It works for many people, and for many people that it is all they need.
The video below covers the major enhancements:
And this is a Twitch stream:
We hope that you all enjoy the new editor. Your feedback is always welcome.
p.s. We have additional "collapsible" spoiler support coming SoonTM. We just didn't quite get it in for release today.
p.p.s If you are running NoScript you will most likely need to whitelist "cachefly" so that the new editor script will run.
UPDATE 9:00pm EST: I've moved some of the initial feedback to here in an effort to keep this thread focused on unresolved issues.
UPDATE 9:30pm EST: After seeing some of the editor load times after going live across 300,000 sites we've made a change that should speed up average load times on the editor significantly.
UPDATE 7:04am EST: We've added an option in Admin -> Features -> Forums -> Settings that will allow you to disable the WYSIWYG site wide on your site. The default state is "ON", but for those of you who feel that you have no need for a WYSIWYG this will allow you to go back to that option site wide.
Last edited by GL_Stephen on Mon Oct 14, 2013 2:30 pm; edited 7 times in total