Menu
When it comes to WYSIWYG editors WYSI rarely WYG. The problem I always have is when people paste in formatted text from word.
Ideally, what I'm looking for is a way for people to input text into the document while at the same time teaching them structure... I just don't know if that's a realistic goal ( compared to cut n' paste )
I'm curious if people have found using something other than WYSIWYG editors ( take SO, for example ) has worked for REAL WORLD USERS. I'm not talking about programmers, developers and experience internet users... I'm talking about your average user.
I'd be interested in best practices when it comes to getting users to enter content... and I'd love it if someone could point me to some good editors/examples.
there are lots of choices when it comes to WYSIWYG ( ckEditor, FreeTextBox, TinyMCE ) but I don't hear a lot about SO-like techniques.
Does adding that small barrier scares users away?
Is it too difficult to teach people to mark up their text?
Is it easier to teach them html?
Is a BBCode implementation a good idea?
What are some Pros/Cons to wysiwyg/markup.
What approach have others used?
462
WYSIWYG (pronounced wiz-ee-wig) is a type of editing software that allows users to see and edit content in a form that appears as it would when displayed on an interface, webpage, slide presentation or printed document. WYSIWYG is an acronym for "what you see is what you get."
First of all, a wysiwyg editor is an illustrative editor for those who want to make Web pages quickly and effectively without needing knowledge in HTML. Well first of all, they aren't that effective at all, all editors alike are restricted to what it can do – wysiwyg editors don't have every feature built in.
Simply put, Markdown is more intuitive than HTML and more convenient than WYSIWYG editors. You don't have to memorize a bunch of complex tags, you can keep your fingers on the keys, and it's portable across services. To help out in the beginning, you might keep a Markdown cheat sheet around as a reference.
Microsoft Word is a common example that helps to define a WYSIWYG editor. You have a blank page with some formatting tools that allow you to add and format words, tables, images, and so forth. What you see on the screen is exactly what you see when you print or share the document.
There are many good markup languages and generally the more natural the markup is the higher the probability that users will use to do markup.
A very common (used also by SO) is Markdown. Another good one (though much less known) is Texy!.
Generally it depends on the application you want to use and the relationship users have to your app. For things that users will have to edit (say as a part of their job or something) I think a Markup language is reasonable since the benefits will son outweigh the costs of learning.
However for places where it is already hard to motivate people to edit it (say like a wiki) a reasonable WYSIWYG is often a better solution.
Another good point is to still use an editing pallete to help out with the markup language (SO is again a good example; for a really interesting implementation see Jumpchart.com)
114
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
