Coevolving Innovations

… in Business Organizations and Information Technologies

Is wiki markup dead?

Today, I’ve been playing around with beta candidate for Quickr, which is a follow-on to the Lotus Quickplace product … but what a leap ahead in product functionality!

Quickr components 1 to 6

Quickr components 7 to 8

I’ve been mainly interested in Quickr because, in the new announcements on the Lotus family, it’s the product with the wiki. (Lotus Connections has multi-user blogs, but not a wiki. Further, Quickr also has feeds — that should more correctly be called aggregators).

I get the feeling that the architects working on Quickr are a different group from those working on Connections, because the list of “components” 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 … or maybe the designers just chose to take a different tack.

Although wikis would seem to be new to the vocabulary of non-techies (maybe circa 2005-2006, with the rise of Wikipedia), the original wikiwiki by Ward Cunningham on C2 goes back to August 1996. I had once tried to customize Mediawiki (which is the engine underneath Wikipedia), have a lot of experience with PmWiki, and am now a major fan of Dokuwiki. Along with the original design of wiki technology came wiki syntax (also known as wiki markup, which varies engine by engine), so that instead of writing the arcane HTML syntax1, e.g. to create a unordered list …

[ul]
[li]requires using codes that are unambiguous to browsers[/li]
[li]but that normal humans should never have to read[/li]
[/ul]

… a simpler alternative is wiki markup, e.g. creating a bulleted list with an asterisk in column one …

* with a syntax where checking for closure isn't required.

The wiki engine translates the wiki markup into XHTML. This may seem simpler for the novice, but it gets frustrating that …

(a) wiki markup isn’t standard across different wiki engines — so much so that an initiative for a wiki creole has evolved;

(b) when you want to do something more complicated like having a table where a cell spans multiple rows or multiple columns, the syntax doesn’t look nearly as simple; and

(c) after you get tired of writing wiki markup, it’s almost impossible to get a WYSIWYG (what you see is what you get) interface on top of the wiki engine that you’ve chosen.

I’ve been using Drupal, an open source content management system, on many of the newer web sites that I’ve been creating. Choosing the package was partially motivated by the fact that a series of IBM Developerworks articles were written about the package. Drupal still has the user writing XHTML, but has the added option of choosing to plug in one of two WYSIWYG modules: TinyMCE or FCKEditor. For small jobs, I can hand-code XHTML. When the amount of text gets really large, though, it’s better to use the WYSIWYG editor so that I can focus more on content than on formatting.

After having spent a year trying to write a book with two collaborator using Dokuwiki, we’ve switched to the book module in Drupal. Like a wiki, Drupal retains the history of edits preceding the current version, and can expose the version-to-version changes with a diff module. In addition, the book module 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.

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’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.

Blogging killed wiki markup.


1 Of course, in standard XHTML, it’s angle brackets with “less than” and “greater than” signs rather than left square bracket and right square bracket … but I can’t seem to get the WYSIWYG editor in WordPress to show the real thing. You win some, you lose some!

3 Comments

  • I, too, hate WikiMarkup, and see it as a barrier to entry for using wikis among users who don’t want to become wiki wonks. But I have looked at a lot of WYSIWYG editors for wikis and I don’t like them either. They’re fragile and limited and funky and usually ill-supported. Just look at your own footnote: you’re telling me the WYSIWYG editor wouldn’t let you type “greater-than” or “less-than”?! The standard reply is, “Hey, it’s open source, if you don’t like it you can fix it or write a better one!” I think that’s a cop-out.

    Wiki WYSIWYG editors are almost universally based on the rich-text editor module built in to modern browsers. That means in addition to each having its own bugs and limitations they all share a set of underlying bugs and limitations. For example, they have no command to create a “Dictionary List” (HTML tags DL and DT) becuase the browser’s rich-text editor API doesn’t export that feature.

    Also, the WYSIWYG aspect is limited by the fact that they aren’t truly integrated with the wiki: if you use wiki plugins for image control or floating boxes or sidebars or anything else, you have to use specially-formatted text tags – not truly WYSIWYG.

    The lack of integration with the wiki is even more obvious in some other cases, including a JSPWiki used at my company: links in WYSIWYG pages aren’t visible to the wiki’s cross-reference generator, making networks of WYSIWYG-edited pages invisible to the “site map” navigation structures.

    In short, they’re just not first-class features of the wiki system with complete, bug-free implementations and full integration.

    Why? I have some theories. First of all, many wikis originated before the rich-text editing widgets of the browsers existed, so plain text INPUT fields were all they had. Second, I think maybe wiki creators and hard-core users have an attitude: “Real men don’t use WYSIWYG.”

    But third and most important, a full-featured, integrated WYSIWYG editor is hard and not fundamentally necessary. When it comes to things that are hard, open source is best suited to building things the community members themselves want (like compilers and Eclipse), not things that are good for non-technical people who don’t want to be wiki wonks. It takes paying customers to motivate technical people to write things for non-technical people – that’s how you get FrontPage instead of Notepad. Or Quickr, for that matter!

    I haven’t seen WYSIWYG editors get better (or enough better) in the last two years, so I don’t think wiki markup is dying very fast. I find that frustrating and sad.

  • You’ve raised the same question I’ve been wondering about myself for the last year or so. Having been an evangelist for the wiki concept at my organization, pitching it as an easy way for content owners to manage their stores in an open, accessible manner–thereby furthering knowledge management goals–I’ve run head-on into the problem of molding wikis to be useful for nontechnical people. I wrote a rather long article about the initial process last year, too, which you may enjoy: “Web-Based Collaborative Editing: Twiki, Tiddly or TikiWiki

    It was my belief from the beginning that the wiki would only be useful if it included some kind of rich-text editor, since I worried whether any of these busy people would bother trying to learn wiki syntax. Now I’m replacing the very simple Dojo rich-text editor with the much more full-featured TinyMCE, and I’m wondering if there’s anybody here who will want to retain their original wiki syntax (some of the content was entered with wiki syntax). As you know, TinyMCE will garble things like bullet lists, and the users will have to recreate them as HTML constructs.

    My belief is that wiki syntax was useful before WYSIWYG editors became feasible as a toolset. Now that they are (the last holdout, Safari, has now joined the pack with version 3.0), I can’t imagine that anyone would really prefer to write wiki syntax rather than using a WYSIWYG editor. Wiki syntax arose (like all of the other HTML-shorthand syntaxes out there) because typing HTML isn’t much fun. But compared with selecting a bullet list item from a toolbar, having to type an asterisk at the beginning of each line isn’t great either. And suppose you need a nested list… ? Etc.

    Of course, I’m removing from TinyMCE all of the controls that can cause trouble: Font coloring, font faces, font sizes, in particular. After all, our style sheet takes care of the style aspects. :-)

    Cheers,
    Leland

  • WYSIWYG example of Google could be useful for a lot of people, no technical people, but if i want a very quickly way of document a project and share with developers, WYSIWYG is awful, very unproductive. I create, in less than hour, a very clear understanding of my project using Wiki Syntax of Google and is very easy create links, TOCS or index. And with the command limitations, create a unique way of write that kind of information, making a common visualizations for all.

    I think that wiki can’t die if we want productivity in the computer science times.
    Sorry my english… :)


Leave a Reply

Your email address will not be published. Required fields are marked *

  • Recent Posts

  • Archives

  • RSS qoto.org/@daviding (Mastodon)

    • New status by daviding April 21, 2019
      Public libraries can become hubs for peer-to-peer learning. In the Let's Learn Teach Online program, #TorontoLibrary has partnered with #P2PU, #CiscoNetAcad, #TorontoESS, and #GBCollege to facilitate "Linux Unhatched" and "Introduction to IoT". Larysa Essex shared their experiences at the @gtalug meeting on April 9, 2019. https://daviding.wordpress.com/2019/04/20/2019-04-09-larysa-essex-linux-unhatched-learning-circles-at-toronto-public-library-web-video/
    • New status by daviding April 1, 2019
      Afternoon break in 200-year-old mid-lake pavilion included zhong, quail eggs, kumquats, sesame peanut blocks, preserved plums. Following afternoon visiting two art museums, the snack re-energized us into discussing philosophy, following the tradition of those frequenting Chinese teahouses. (Yuyuan Tea House, Yu Garden, Shanghai, PR China) 20190331 @marcocataffo
    • New status by daviding April 1, 2019
      Here in Shanghai, @marcocataffo has a Thinkpad T430 , which I've now brought up to date with Manjaro Linux (and Kubuntu LTS as a backup) alongside Windows 7. He's now 2 days jet lagged from Italy. Eventually, maybe @antlerboy will meet somewhere.
    • daviding shared a status by antlerboy@mastodon.social February 9, 2019
      @daviding Wittgenstein:"6.54 My propositions are elucidatory in this way: he who understands me finally recognizes them as senseless, when he has climbed out through them, on them, over them. (He must so to speak throw away the ladder, after he has climbed up on it.)"
    • New status by daviding February 9, 2019
      Dinner with @rms @fsf inviting the activists #CivicTechTO to gain some insight into discussions on privacy concerns #QuaysideToronto. We outlined but didn't delved into the complexity of three levels of government involved in #WaterfrontTO. (Royal Myanmar, Homer Avenue, Etobicoke, Ontario) 20190208
  • RSS on IngBrief

    • Contextual dyadic thinking (Lee, 2017)
      Contextual dyadic thinking is proposed by Keekok Lee in her 2017 The Philosophical Foundations of Classical Chinese Medicine. This is as a way of appreciating Chinese implicit logic, as an alternative to dualistic thinking that has developed over centuries in Western philosophy.
    • Dao, de, wei, wuwei (Lai 2003)
      Appreciating wei and wuwei has led to the context of dao and de, in the writings of Karyn L. Lai. The scholarly review acknowledges prior interpretations of de and dao.
    • Engineering Resilience vs. Ecological Resilience (Holling, 1996)
      For @theNASciences in 1996, #CSHolling clarified definitions of resilience, with engineering seeking one equilibrium state, while ecology recognizes many. Those who emphasize the near-equilibrium definition of engineering resilience, for example, draw predominantly from traditions of deductive mathematical theory (Pimm,. 1984) where simplified, untouched ecological systems are imagined, or from traditions of engineering, where the motive […]
    • Service coproductions as reciprocal activities
      In addition to extrinsic economic exchange, #JohnMCarroll #JiaweiChen #ChienWenTinaYuan #BenjaminHanrahan @ISTatPENNSTATE say service coproductions relying on all participants to collaborate in both economic exchange and social exchange. Service coproduction is a special case of service provision in which the roles of service provider and service recipient both require active participation. Examples include healthcare, education, and […]
    • Science and Society in East and West | Joseph Needham | 2004
      In researching #SystemsChange, fundamental differences in science and philosophy in the west and the Chinese were surfaced by #JosephNeedham. A useful translation of wéi and wú wéi (i.e. 為 and 無為 , or 为 and 无为) is the ways of "human will" and "nature" as juxtaposed.
    • Wiki as computational platform
      Thinking forward on #federatedwiki, rather than backwards by @wardcunningham. > [Federated wiki] is a computational platform for the collaborative construction of things that work and will continue to work as platform technology evolves underneath it. > Too much thinking about wiki as a note-taking system will just hold it back.
  • RSS on Media Queue

  • RSS on daviding.com

    • 2019/03 Moments March 2019
      Month of intensive lectures and research meetings, in Toronto and then in Shanghai, with social breaks on local excursions to clear minds.
    • 2019/02 Moments February 2019
      Reduced exercise outside with a cold and snowy February, with excursions out of the house to warm places with family, friends and colleagues.
    • 2019/01 Moments January 2019
      January in Toronto has lots of intellectual offerings and artistic exhibitions to attract the curious out of warm homes, through cold and snow.
    • 2018/12 Moments December 2018
      Tried to have a normal month, with a busy social calendar of birthdays, a funeral plus Christmas season, while daily temperatures hovered just above freezing.
    • 2018/11 Moments November 2011
      Mentally busy month with a conference coming to town, and maintaining the regular pattern of local meetings, travel around town only by bicycle.
    • 2018/10 Moments October 2018
      October had more bicycling cross-town as fall temperatures declined, plus a 6-day trip to Portland Oregon for pattern language conferences.
  • Meta

  • Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License
    Theme modified from DevDmBootstrap4 by Danny Machal