💾 Archived View for jb55.com › ward.asia.wiki.org › wiki-design-principles captured on 2021-12-04 at 18:04:22. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Wiki has turned out to be much more than I'd imagined! That is not to say that I didn't imagine a lot. These are the design principles I sought to satisfy with the first release of Wiki. -- Ward Cunningham Note that this page is only a reconstruction from memory of intentions I held at the beginning. Additional principles, like server robustness, have been forced upon me.
<b>Simple</b> - easier to use than abuse. A wiki that reinvents HTML markup (<i>[b]bold[/b]</i>, for example) has lost the path!
<b>Open</b> - Should a page be found to be incomplete or poorly organized, any reader can edit it as they see fit.
<b>Incremental</b> - Pages can cite other pages, including pages that have not been written yet.
<b>Organic</b> - The structure and text content of the site are open to editing and evolution.
<b>Mundane</b> - A small number of (irregular) text conventions will provide access to the most useful page markup.
<b>Universal</b> - The mechanisms of editing and organizing are the same as those of writing, so that any writer is automatically an editor and organizer.
<b>Overt</b> - The formatted (and printed) output will suggest the input required to reproduce it.
<b>Unified</b> - Page names will be drawn from a flat space so that no additional context is required to interpret them.
<b>Precise</b> - Pages will be titled with sufficient precision to avoid most name clashes, typically by forming noun phrases.
<b>Tolerant</b> - Interpretable (even if undesirable) behavior is preferred to error messages.
<b>Observable</b> - Activity within the site can be watched and reviewed by any other visitor to the site.
<b>Convergent</b> - Duplication can be discouraged or removed by finding and citing similar or related content. There are many Wiki authors and implementers. Here are some additional principles that guide them, but were not of primary concern to me.
<b>Trust</b> - This is the most important thing in a wiki. Trust the people, trust the process, enable trust-building. Everyone controls and checks the content. Wiki relies on the assumption that most readers have good intentions. <i>But see: Assume Good Faith Limitations</i>
<b>Fun</b> - Everybody can contribute; nobody has to.
<b>Sharing</b> - of information, knowledge, experience, ideas, views... Comments:
<b>Interaction</b> - This enables guest interaction.
<b>Collaboration</b> - We believe that this could make a good collaboration tool, both synchronously and asynchronously.
<b>Platforms</b> - We like the cross-platform implications.
<b>Social Networks</b> - Its power for supporting collaboration is great.
<hr>
See also:
<hr>
In the list above <i>Unified</i> and <i>Precise</i> are the least generic and convincing points, especially if one thinks of how they apply to non-English wikis or to other engines like Media Wiki. Perhaps they can be reformulated as sub-points of <i>Convergent</i>? Cf. its opposite: «Meat Ball:View Point is nothing like a wiki».
[[http://www.project-download.com/php-projects/ www.project-download.com] php projects]
<hr>
Category History Category Wiki Concept
See original on c2.com