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 *

  • RSS qoto.org/@daviding (Mastodon)

    • daviding: “Web video introduction of 15 minutes for 1-hour Lunch and Le…” March 22, 2024
      Web video introduction of 15 minutes for 1-hour Lunch and Learn #CentreForSocialInnovationToronto on "Systems Changes Dialogues for Social Innovation" invites practitioners for upcoming monthly meetings. Evocative animated images, details deferred to conversations with mentors. https://coevolving.com/blogs/index.php/archive/systems-changes-dialogues-csi/#SystemsThinking
    • daviding: “Web video of slides from "From Unfreezing-Refreezing, to Sys…” March 21, 2024
      Web video of slides from "From Unfreezing-Refreezing, to Systems Changes Learning" for Dialogic Drinks of #EQLab represents only 1/5 of the time compared to peer-led discussions. Concise hosting called for brevity, and richer presentations. https://coevolving.com/blogs/index.php/archive/from-unfreezing-refreezing-eq-lab/ #SystemsThinking
    • daviding: “Hosting multiple Dialogic Drinks on "From Unfreezing-Refreez…” March 8, 2024
      Hosting multiple Dialogic Drinks on "From Unfreezing-Refreezing, to Systems Changes Learning" online, March 12 (Europe), March 14 (Americas), March 15 (Australia). #Leadership meets #SystemsThinking . Short presentations, longer discussions https://www.eqlab.co/from-unfreezing-refreezing-to-systems-changes-learning-david-ing
    • daviding: “"Climate change has no map that we know of. Each time a new…” February 15, 2024
      "Climate change has no map that we know of. Each time a new scientific study returns something we studied before, it's always going to arrive faster and be worse than we thought before". Episode 5, #DavidLHawk "What to do When It's too Late" https://www.youtube.com/watch?v=VPruvIsDRDk #SystemsThinking "Instead of cause-effect thinking, effects coming from prior effects, not […]
    • daviding: “In the third episode of "What to Do When It's Too Late", #Da…” February 2, 2024
      In the third episode of "What to Do When It's Too Late", #DavidLHawk explains his #systemsthinking with humans in #climatechange, dealing with hopelessness. Live weekly broadcast on #BoldBraveTv with video recordings and podcasts. Text digest at https://daviding.wordpress.com/2024/02/02/what-to-do-when-its-too-late-david-l-hawk-2024/
  • RSS on IngBrief

    • Introduction, “Systems Thinking: Selected Readings, volume 2”, edited by F. E. Emery (1981)
      The selection of readings in the “Introduction” to Systems Thinking: Selected Readings, volume 2, Penguin (1981), edited by Fred E. Emery, reflects a turn from 1969 when a general systems theory was more fully entertained, towards an urgency towards changes in the world that were present in 1981. Systems thinking was again emphasized in contrast […]
    • Introduction, “Systems Thinking: Selected Readings”, edited by F. E. Emery (1969)
      In reviewing the original introduction for Systems Thinking: Selected Readings in the 1969 Penguin paperback, there’s a few threads that I only recognize, many years later. The tables of contents (disambiguating various editions) were previously listed as 1969, 1981 Emery, System Thinking: Selected Readings. — begin paste — Introduction In the selection of papers for this […]
    • Concerns with the way systems thinking is used in evaluation | Michael C. Jackson, OBE | 2023-02-27
      In a recording of the debate between Michael Quinn Patton and Michael C. Jackson on “Systems Concepts in Evaluation”, Patton referenced four concepts published in the “Principles for effective use of systems thinking in evaluation” (2018) by the Systems in Evaluation Topical Interest Group (SETIG) of the American Evaluation Society. The four concepts are: (i) […]
    • Quality Criteria for Action Research | Herr, Anderson (2015)
      How might the quality of an action research initiative be evaluated? — begin paste — We have linked our five validity criteria (outcome, process, democratic, catalytic, and dialogic) to the goals of action research. Most traditions of action research agree on the following goals: (a) the generation of new knowledge, (b) the achievement of action-oriented […]
    • Western Union and the canton of Ticino, Switzerland
      After 90 minutes on phone and online chat with WesternUnion, the existence of the canton of Ticino in Switzerland is denied, so I can’t send money from Canada. TicinoTurismo should be unhappy. The IT developers at Western Union should be dissatisfied that customer support agents aren’t sending them legitimate bug reports I initially tried the […]
    • Aesthetics | Encyclopaedia Britannica | 15 edition
      Stephen C. Pepper was a contributor to the Encyclopaedia Britannica, 15th edition, on the entry for Aesthetics.
  • Recent Posts

  • Archives

  • RSS on daviding.com

    • 2024/02 Moments February 2024
      Chinese New Year celebrations, both public and family, extended over two weekends, due to busy social schedules.
    • 2024/01 Moments January 2024
      Hibernated with work for most of January, with more activity towards the end of month with warmer termperatures.
    • 2023/12 Moments December 2023
      A month of birthdays and family holiday events, with seasonal events at attractuions around town.
    • 2023/11 Moments November 2023
      Dayliight hours getting shorter encouraged more indoor events, unanticipated cracked furnace block led to replacement of air conditioner with heat pump, too.
    • 2023/10 Moments October 2023
      Left Seoul for 8 days in Ho Chi Minh City, and then 7 days in Taipei. Extended family time with sightseeing, almost completely offline from work.
    • 2023/09 Moments September 2023
      Toronto International Film Festival, and the first stop of a 3-week trip to Asia starting with Seoul, Korea
  • RSS on Media Queue

    • What to Do When It’s Too Late | David L. Hawk | 2024
      David L. Hawk (American management theorist, architect, and systems scientist) has been hosting a weekly television show broadcast on Bold Brave Tv from the New York area on Wednesdays 6pm ET, remotely from his home in Iowa. Live, callers can join…Read more ›
    • 2021/06/17 Keekok Lee | Philosophy of Chinese Medicine 2
      Following the first day lecture on Philosophy of Chinese Medicine 1 for the Global University for Sustainability, Keekok Lee continued on a second day on some topics: * Anatomy as structure; physiology as function (and process); * Process ontology, and thing ontology; * Qi ju as qi-in-concentrating mode, and qi san as qi-in-dissipsating mode; and […]
    • 2021/06/16 Keekok Lee | Philosophy of Chinese Medicine 1
      The philosophy of science underlying Classical Chinese Medicine, in this lecture by Keekok Lee, provides insights into ways in which systems change may be approached, in a process ontology in contrast to the thing ontology underlying Western BioMedicine. Read more ›
    • 2021/02/02 To Understand This Era, You Need to Think in Systems | Zeynep Tufekci with Ezra Klein | New York Times
      In conversation, @zeynep with @ezraklein reveal authentic #SystemsThinking in (i) appreciating that “science” is constructed by human collectives, (ii) the west orients towards individual outcomes rather than population levels; and (iii) there’s an over-emphasis on problems of the moment, and…Read more ›
    • 2019/04/09 Art as a discipline of inquiry | Tim Ingold (web video)
      In the question-answer period after the lecture, #TimIngold proposes art as a discipline of inquiry, rather than ethnography. This refers to his thinking On Human Correspondence. — begin paste — [75m26s question] I am curious to know what art, or…Read more ›
    • 2019/10/16 | “Bubbles, Golden Ages, and Tech Revolutions” | Carlota Perez
      How might our society show value for the long term, over the short term? Could we think about taxation over time, asks @carlotaprzperez in an interview: 92% for 1 day; 80% within 1 month; 50%-60% tax for 1 year; zero tax for 10 years.Read more ›
  • 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