For those who choose to install your own wiki engine or who choose to create a wiki on a wiki hosting service that requires wiki syntax, you'll need to learn a little about wikitext. Although there may be a short learning curve on using wikitext to produce a page, it is nowhere close to the learning curve required to learn HTML. I wish I could give to you the cheat-sheet of everything you need to know about wiki syntax on this blog. Unfortunately, there is no standard wikitext used across wiki engines or wiki farms. In the early days of wiki, this was often a complication for people involved in more than one wiki. This lack of standardized formatting across wiki software also makes it difficult to transfer wiki content across platforms or wiki servers.
Wikitext uses ordinary punctuation to format text on a wiki page. Examples of how basic formatting is performed on some wikis are discussed below with some noted differences:
- Bold text
Bolding of text may require using HTML tags, such as <> to start bold text, followed by the < /b > to stop on some wikis. One wiki application requires that a pair of two single quotes be placed around the text to be bold. Another wiki service will bold text that is preceded and followed by a pair of asterisks (**bold** = bold). - Italized text
Italicing text is often defined by using a single pair of quotes around the text (‘italics’ = italics) but by underscores on another wiki (_italics_ = italics) - Unordered list
Using the asterisk symbol may define an item in a bulleted list on some wiki applications. Other wikis let you use the HTML tags to define lists (e.g., <_ul_>, <_li_>, <__/>) - Ordered list
Using the # symbol may define an item in a numbered list on some wikis. However, on other wikis, the asterisk (*) is used for an ordered list. Some wikis permit you to use the HTML tags to define ordered lists (e.g., <_ol_>, <_li_>, <_>) - Horizontal line
Adding 4 dashes to the page may define a horizontal line on some wiki applications.
Because of the differences across wiki engines and wiki services, you would need to consult the documentation for specific information about the tags required.
For those who have no interest in learning and using any tags or codes at all, even though it might be recognized as the simplified version, HAVE NO FEAR! You can create super wikis without any knowledge of wikitext. No tags are required! In my opinion, it is really unnecessary to give wiki syntax another thought. Most of the wiki farms today allow you to create a wiki without knowing any wikitext. Some give both options -- for those techie / geeky types who must write code or tags when developing web content. Most wiki hosting services now offer a WYSIWYG (what-you-see-is-what-you-get) editor where all you need to do is click on the "Edit" button and type your text. A task bar is generally available for you to easily customize your text (bold, italics), to align your text (left-justified, right-justified, center), and to add lists (bullets or numbers). It's also usually very simple to add images and include links in your content without knowing any tags.
Even if you love coding and enjoy the challenge of using tags, think about your wiki community. When given a choice, choose the most simple approach -- the new approach -- no tags. By using wiki services which don't require any tags or wikitext, your wiki community can expand greatly.
Here's a short video from my friends at Wetpaint that describes how the old approach of using wiki syntax for creating wikis differs from the newer approach:
As posted on YouTube by wpseattle
It sounds like an easy decision to me. For more information, visit the Everything Wiki site for a listing of the popular wiki services and see how many choices you have in creating wikis with WYSIWYG editors. It's hosted on Wetpaint where no tags are required. While there, join the community. : )
Note: Extra spacing and creativity (_) were required around the HTML tags to demonstrate them on the blog -- and they may potentially not display completely.
Image credit: full circle magazine
No comments:
Post a Comment