{"id":62,"date":"2007-04-02T20:33:17","date_gmt":"2007-04-03T01:33:17","guid":{"rendered":"http:\/\/coevolving.com\/blogs\/index.php\/archive\/is-wiki-markup-dead\/"},"modified":"2007-04-02T20:33:17","modified_gmt":"2007-04-03T01:33:17","slug":"is-wiki-markup-dead","status":"publish","type":"post","link":"https:\/\/coevolving.com\/blogs\/is-wiki-markup-dead\/","title":{"rendered":"Is wiki markup dead?"},"content":{"rendered":"<p>Today, I&#8217;ve been playing around with beta candidate for <a href=\"http:\/\/www-142.ibm.com\/software\/sw-lotus\/products\/product3.nsf\/wdocs\/quickr\" title=\"ibm.com\">Quickr<\/a>, which is a follow-on to the <a href=\"http:\/\/www-142.ibm.com\/software\/sw-lotus\/products\/product3.nsf\/wdocs\/ltwhome\" title=\"ibm.com\">Lotus Quickplace<\/a> product &#8230; but what a leap ahead in product functionality!<\/p>\n<p><a href=\"http:\/\/coevolving.com\/blogs\/wp-content\/uploads\/2007\/04\/quickr_components_1-6.jpg\" title=\"Quickr components 1 to 6\" rel=\"lightbox[62]\"><img decoding=\"async\" src=\"http:\/\/coevolving.com\/blogs\/wp-content\/uploads\/2007\/04\/quickr_components_1-6.jpg\" alt=\"Quickr components 1 to 6\" \/><\/a><\/p>\n<p><a href=\"http:\/\/coevolving.com\/blogs\/wp-content\/uploads\/2007\/04\/quickr_components_7-8.jpg\" title=\"Quickr components 7 to 8\" rel=\"lightbox[62]\"><img decoding=\"async\" src=\"http:\/\/coevolving.com\/blogs\/wp-content\/uploads\/2007\/04\/quickr_components_7-8.jpg\" alt=\"Quickr components 7 to 8\" \/><\/a><\/p>\n<p>I&#8217;ve been mainly interested in Quickr because, in the new announcements on the Lotus family, it&#8217;s the product with the wiki.  (<a href=\"http:\/\/www-142.ibm.com\/software\/sw-lotus\/products\/product3.nsf\/wdocs\/connectionshomehttp:\/\/www-142.ibm.com\/software\/sw-lotus\/products\/product3.nsf\/wdocs\/connectionshome\" title=\"ibm.com\">Lotus Connections<\/a> has multi-user blogs, but not a wiki.  Further, Quickr also has feeds \u00e2\u20ac\u201d that should more correctly be called aggregators).<\/p>\n<p>I get the feeling that the architects working on Quickr are a different group from those working on Connections, because the list of &#8220;components&#8221; feels more like options commonly in use on the web, rather than those used by large-scale enterprises.  Maybe this comes from the quick-and-dirty style that Quickplace seems to exude &#8230; or maybe the designers just chose to take a different tack.<\/p>\n<p>Although wikis would seem to be new to the vocabulary of non-techies (maybe circa 2005-2006, with the rise of <a href=\"http:\/\/en.wikipedia.org\/wiki\/Main_Page\" title=\"wikipedia.org\">Wikipedia<\/a>), the <a href=\"http:\/\/c2.com\/cgi\/wiki?WikiArchive\" title=\"c2.com\">original wikiwiki by Ward Cunningham on C2 goes back to August 1996<\/a>.  I had once tried to customize <a href=\"http:\/\/www.mediawiki.org\/wiki\/MediaWiki\" title=\"mediawiki.org\">Mediawiki<\/a> (which is the engine underneath Wikipedia), have a lot of experience with <a href=\"http:\/\/pmwiki.org\/\" title=\"pmwiki.org\">PmWiki<\/a>, and am now a major fan of <a href=\"http:\/\/wiki.splitbrain.org\/wiki:dokuwiki\" title=\"splitbrain.org\">Dokuwiki<\/a>.  Along with the original design of wiki technology came <a href=\"http:\/\/www.usemod.com\/cgi-bin\/mb.pl?WikiSyntax\" title=\"usemod.com\">wiki syntax<\/a> (also known as <a href=\"http:\/\/www.usemod.com\/cgi-bin\/mb.pl?WikiMarkupStandard\" title=\"usemod.com\">wiki markup, which varies engine by engine<\/a>), so that instead of writing the arcane HTML syntax<a href=\"#footnote1\"><sup>1<\/sup><\/a>, e.g. to create a unordered list &#8230;<br \/>\n<code><br \/>\n[ul]<br \/>\n[li]requires using codes that are unambiguous to browsers[\/li]<br \/>\n[li]but that normal humans should never have to read[\/li]<br \/>\n[\/ul]<br \/>\n<\/code><br \/>\n&#8230; a simpler alternative is wiki markup, e.g. creating a bulleted list with an asterisk in column one &#8230;<br \/>\n<code><br \/>\n* with a syntax where checking for closure isn't required.<br \/>\n<\/code><br \/>\nThe wiki engine translates the wiki markup into XHTML.  This may seem <a href=\"http:\/\/fishbowl.pastiche.org\/2004\/03\/19\/in_defense_of_wiki_markup\" title=\"fishbowl.pastiche.org\">simpler for the novice<\/a>, but <a href=\"http:\/\/wellbourne.dyndns.org\/~rsanders\/blog\/archives\/000298.html\" title=\"wellbourne.dyndns.org\">it gets frustrating<\/a> that &#8230;<\/p>\n<p>(a) wiki markup isn&#8217;t standard <a href=\"http:\/\/www.wikimatrix.org\/\" title=\"wikimatrix.org\">across different wiki engines<\/a> \u00e2\u20ac\u201d so much so that an initiative for a <a href=\"http:\/\/www.wikicreole.org\/\" title=\"wikicreole.org\">wiki creole<\/a> has evolved;<\/p>\n<p>(b) when you want to do something more complicated like having a <a href=\"http:\/\/www.pmwiki.org\/wiki\/PmWiki\/TableDirectives\" title=\"pmwiki.org\">table where a cell spans multiple rows or multiple columns<\/a>, the syntax doesn&#8217;t look nearly as simple; and<\/p>\n<p>(c) after you get tired of writing wiki markup, it&#8217;s almost impossible to get a <a href=\"http:\/\/www.usemod.com\/cgi-bin\/mb.pl?WysiwygWiki\" title=\"usemod.com\">WYSIWYG (what you see is what you get) interface on top<\/a> of the wiki engine that you&#8217;ve chosen.<\/p>\n<p>I&#8217;ve been using <a href=\"http:\/\/drupal.org\" title=\"drupal.org\">Drupal<\/a>, an open source content management system, on many of the newer web sites that I&#8217;ve been creating.  Choosing the package was partially motivated by the fact that a series of <a href=\"http:\/\/www-128.ibm.com\/developerworks\/ibm\/osource\/implement.html\" title=\"ibm.com\">IBM Developerworks articles were written about the package<\/a>.  Drupal still has the user writing XHTML, but has the added option of choosing to plug in one of two WYSIWYG modules:  <a href=\"http:\/\/drupal.org\/project\/tinymce\" title=\"drupal.org\">TinyMCE<\/a> or <a href=\"http:\/\/drupal.org\/project\/fckeditor\" title=\"drupal.org\">FCKEditor<\/a>.  For small jobs, I can hand-code XHTML.  When the amount of text gets really large, though, it&#8217;s better to use the WYSIWYG editor so that I can focus more on content than on formatting.<\/p>\n<p>After having spent a year trying to write a book with two collaborator using <a href=\"http:\/\/wiki.splitbrain.org\/wiki:dokuwiki\" title=\"splitbrain.org\">Dokuwiki<\/a>, we&#8217;ve switched to the <a href=\"http:\/\/drupal.org\/node\/284\" title=\"drupal.org\">book module in Drupal<\/a>.  Like a wiki, Drupal retains the history of edits preceding the current version, and can expose the version-to-version changes with a <a href=\"http:\/\/drupal.org\/project\/diff\" title=\"drupal.org\">diff module<\/a>.  In addition, the <a href=\"http:\/\/drupal.org\/node\/284\" title=\"drupal.org\">book module<\/a> allows pages to be promoted to being a parent, or demoted to be a child, automatically inserting navigation links from the page, forward, backwards, or to the parent.<\/p>\n<p>So, with WYSIWYG plug-ins available as open source software, is there a reason to still be writing wiki markup?  I think the case for wiki markup is getting weaker by the day.  The majority of people who have never seen wiki markup won&#8217;t miss it.  Blogs are more popular than wikis, and blogs are mostly written as XHTML through a WYSIWYG editor or an offline program.  Since Quickr offers both blog and wiki features within a single product, it makes sense to go with WYSIWYG and take the  markup out of wiki.<\/p>\n<p>Blogging killed wiki markup.<\/p>\n<hr \/>\n<p><a id=\"footnote1\"><sup>1<\/sup><\/a> Of course, in standard XHTML, it&#8217;s angle brackets with &#8220;less than&#8221; and &#8220;greater than&#8221; signs rather than left square bracket and right square bracket &#8230; but I can&#8217;t seem to get the WYSIWYG editor in WordPress to show the real thing.  You win some, you lose some!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WYSIWYG Javascript editors removed the need for wiki markup, and fact that Quickr doesn&#8217;t use markup is a significant milestone.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[14],"tags":[],"class_list":["post-62","post","type-post","status-publish","format-standard","hentry","category-technologies"],"_links":{"self":[{"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":0,"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/posts\/62\/revisions"}],"wp:attachment":[{"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/media?parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/categories?post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/coevolving.com\/blogs\/wp-json\/wp\/v2\/tags?post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}