StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You may not need to allow direct HTML editing, if you use something like <a href="http://daringfireball.net/projects/markdown/basics" rel="nofollow noreferrer">Markdown</a> or <a href="http://www.textism.com/tools/textile/" rel="nofollow noreferrer">Textile</a> -- users will always work with the plain text representation of the content, while on-demand one-way plain-text-to-html conversion will be possible for nicer looks in HTML pages.</p> <p>There are a number of Ruby Gems to help you in implementing both Markdown and Textile plain-text-to-html conversion, if need be. There are also some nice editors for markdown (as the one which SO uses).</p> <p>In my opinion, plain-text editing (in Markdown, Textile or similar) is sufficient and a better choice in most circumstances. It's definitely a very lightweight and standards-compliant method for creating rich content and although Markdown, Textile and the like do not cover all possible formatting options, the plain text path deserves a serious consideration.</p> <p>You can also see here on StackOverflow—which uses Markdown for questions and answers—that it is a decent one. I strongly support the need to be able to see the "formatting tags", because WYSIWYG almost always leads to misplaced/unneeded tags. Also, using plain text formats allows you to <strong>have 100% control on the resulting HTML</strong>.</p> <p>If you <strong>must</strong> use WYSIWYG, my experience with TinyMCE has been decent enough to recommend it.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload