Loading...
 

WYSIWYG vs Wiki syntax

When should you use wiki syntax vs WYSIWYG?

  • Wiki engines normally save content as wiki syntax (aka wiki text or wiki markup).
  • WYSIWYG editors such as TinyMCE or CKEditor by default save HTML.


There are some things that are better to do in Wiki syntax, and some things that are better to do in HTML. For example, PluginGroup permits you to show certain content to a group of users and other content to another group. This is impossible to with HTML.

Happily, Tiki offers both wiki and WYSIWYG-HTML, and you can even use both on the same page. This page is to help you choose when you should use one or the other.

Wiki

What Wiki doesn't have
Workaround
Instant visibility of what it will look like CodeMirror or Live Preview
Justified or right-aligned text Use PluginDiv
Easy edition of big tables Use Spreadsheet and PluginSheet instead.
In Tiki9: Use PluginWysiwyg instead for the table; and if Tiki version < 9: Use another wiki page in wysiwyg mode for the whole table, and include it with PluginInclude from the previous page

WYSIWYG

What WYSIWYG doesn't have
Workaround
Wiki links, and thus Backlinks Use page aliases when you rename pages so links are not broken. If page aliases are not working for you, use PluginRedirect.
Clean diffs Use HTML diff and expect long pages and false positives
Mobile editing http://dev.tiki.org/wish4168-WYSIWYG-Mobile-check-if-browser-is-supported-and-provide-relevant-error-message
Edit by Section Use PluginInclude instead



New in Tiki9: If you need part of the page as WYSIWYG and part as wiki syntax, you can use PluginWYSIWYG

Improved in Tiki9: WYSIWYG which saves in wiki syntax instead of HTML. To activate: tiki-admin.php?page=wysiwyg -> Use Wiki syntax in WYSIWYG

Related

alias