The word wiki comes from the Hawaiian phrase “wiki wiki,” meaning “quick” or “hurry.” Ward Cunningham adopted the name after seeing “Wiki Wiki Bus” at an airport. The sense of urgency fit the spirit of the system he was creating: a knowledge repository built through shared authorship and constant revision, using the internet to create, accumulate, improve, and distribute knowledge.
Why the wiki idea mattered
The value of a knowledge base hardly needs explanation. It is one of the main ways human civilization preserves and passes on what it knows. Traditionally, knowledge repositories are created by gathering a group of recognized experts, having them compile material within a fixed period, and then issuing revised editions from time to time. Encyclopedias, dictionaries, and textbooks are classic examples.
The wiki view challenged that model on several fronts. Traditional knowledge production is expensive, updates slowly, and often depends on authorities whose authority may not be as absolute as people assume. A wiki uses the internet to expand “a group of experts” into the entire population of connected users. It replaces occasional edition updates with continuous revision.
Behind this is a set of strong beliefs: that useful knowledge exists among ordinary people, that “more eyes will find more errors,” and that when people are given freedom, they can often use it well.
The first problem: why would people contribute for free?
Any wiki faces an immediate practical difficulty: how do you persuade large numbers of people to volunteer their time and knowledge without pay?
The answer built into the wiki model is openness, equality, freedom, and immediate participation. In a wiki, any entry can in principle be edited by anyone at any time. That design lowers the cost of participation as much as possible. You do not need to be selected, commissioned, or formally accredited before you can improve something.
But that freedom creates the second major problem: who manages quality? Who keeps order?
Wiki’s answer resembles a democratic faith. Under shared procedures, policies, and working guidelines, participants can collectively manage both the quality of the content and the progress of the project. The system depends less on a fixed editorial authority and more on rules, discussion, and ongoing correction.
Time is one of wiki’s strongest tools
A wiki also has something traditional projects lack: the ability to accumulate continuously over time.
Because participation is usually amateur, work cannot always be scheduled and completed according to a strict plan. A wiki compensates for that with persistence. Once a wiki project is online, it can keep growing 24 hours a day, 7 days a week, as long as the server remains up. Over time, that accumulation tends not to slow down but to accelerate.
Another reason wikis were accepted so quickly is that knowledge itself was changing faster and faster. As information cycles sped up, people needed faster ways to create, collect, and share what they knew.
How wiki software emerged
In 1995, Ward Cunningham wrote the first wiki program, WikiWikiWeb, in Perl and released it freely as open source software. After that, more programmers developed more open-source wiki systems. Among them, the PHP-based system associated with Wikipedia became the most widely used, largely because of the extraordinary success of Wikipedia itself. Like many other wiki platforms, it was available as free open-source software.
Once such software is installed, creating a wiki community begins much like any other online project: with a front page. In a wiki, the homepage is usually centered on a category structure for the knowledge base.
Because wiki markup is much simpler than HTML, building pages does not require a designer. Anyone can learn the basic syntax quickly enough to create a standard front page. For a first-time builder, the easiest method is often to borrow the structure of another wiki homepage and replace its contents with material suited to the new project.
The homepage is never final
The person who creates the first wiki index page cannot be sure it is the most logical, complete, or scientific arrangement. For that reason, the power to edit the homepage must also be shared with everyone who can see it. At the same time, earlier versions are preserved in the page history so unsuitable changes can be corrected.
That leads directly to a deeper question: who decides what counts as good or bad?
The wiki philosophy assumes that although inappropriate edits may appear during the process, they will eventually be repaired. The expectation is that people will, over time, improve a document rather than degrade it. Documents exist because they are useful to others. If free editing and reorganization make information more useful, then outdated, neglected, obviously incorrect, or obnoxious material will eventually be removed. Wikis also retain defensive tools against malicious editing, such as blocking an IP address to prevent a vandal from returning.
After the homepage and category structure are in place, the real labor begins: writing downward from the directory level into article after article. That is an enormous task, and precisely because it is too large for a small group to finish quickly, the collaborative model becomes necessary.
The English-language Wikipedia, launched on January 15, 2001, had accumulated more than 300,000 articles after a little over three years—roughly three times the size of Encyclopaedia Britannica at the time. At that growth rate, it was expected to reach 1 million entries within months and to span around 50 languages, from Arabic to Gaelic. In June 2004, Wikipedia was receiving an average of 8.7 million visits per day, surpassing the Britannica website.
Neutrality is not optional
Because a wiki is maintained publicly by many people, it cannot function like a discussion forum. If it takes partisan positions as a matter of editorial principle, it will collapse into endless argument.
That is why wiki editing depends on the idea of a neutral point of view. Neutrality does not mean suppressing disagreement. It means that when disputes exist, the article should describe them rather than simply adopt one side as truth.
A classic example makes the distinction clear. Instead of asserting “God exists” or “God does not exist,” a neutral treatment would say something like: many Americans believe that God exists. The emphasis shifts from advocacy to description.
When presenting opposing positions, both should be described in a positive and sympathetic tone. One side should not be written as obviously reasonable while the other appears only as a target for ridicule.
Strict objectivity may be difficult, since human beings are emotional and rarely detached. Neutrality, however, is more practical. It is a technical discipline rather than an emotional state. If people on opposing sides can read the final text and feel that their views have been presented clearly, fully, and in the most sympathetic terms possible, then neutrality has largely been achieved.
This can be guided through workable, measurable procedures: use similarly respectful language for each side, give broadly comparable space to competing views, and include the major arguments that matter. Many strong scholars, encyclopedia editors, and textbook writers already rely on this sort of neutral writing.
Wiki systems recognize that people naturally want to debate, so they usually include discussion pages. But those discussions are attached to the knowledge page rather than replacing it.
Openness still needs administrators
Starting in 2002, Wikipedia began facing deliberate acts of vandalism. Most of that damage was quickly repaired by other users, but in the end the site chose to protect its homepage so that it could no longer be edited freely by anyone; only administrators could modify it. This was, in effect, a reluctant retreat from total openness. Wiki systems can support protection at many levels, though experience suggested that broad protection below the top level was usually unnecessary.
A wiki, like democracy, still needs something equivalent to legislators and institutions. It depends on highly committed administrators.
In most cases, the person who installs the wiki system and creates its homepage becomes the project’s first administrator. That person’s next job is not only to write entries but also to identify, encourage, and develop more administrators from among natural participants, who in turn can help cultivate still more.
The main duties of administrators are to protect pages, delete pages, restore pages, block and unblock users. But administration alone is not enough. They must also lead by example through serious article writing and careful editing.
At the beginning of a wiki project, administrators usually write the first body of content themselves. Their labor creates the project’s initial vitality. Only on that basis can the wiki begin to grow like a snowball.
Every new wiki faces the same deadlock: if there are few entries, no one visits; if no one visits, no one writes; if no one writes, there are still no entries. Breaking that cycle requires difficult early work from administrators. Once the project enters a positive loop, administrators can gradually shift some of their time away from writing toward broader maintenance and governance.
How wiki differs from BBS and blogs
Wiki, BBS, and blogs are all community tools that give more power to ordinary internet users, but they organize participation in very different ways.
A BBS arranges its structure around topics or threads. Registered users post and reply in designated sections. A blog is a lightweight publishing system organized around an individual; its basic form is the personal homepage. A wiki is organized around knowledge points, and its visible form is thousands of volunteers revising thousands of documents.
A blog places the individual first. Whose blog it is becomes its primary attribute, and that gives the owner strong motivation to maintain and build it over time. A BBS emphasizes interaction and resembles a public square, where many people are drawn by the liveliness of exchange and the immediate pleasure of speaking out.
A wiki stresses shared authorship. Large numbers of people work together to maintain and improve a single entry. For that reason, the proportion of users who actively contribute to a wiki is much smaller than in a BBS or blog—possibly well below 1 percent. A wiki is not about bustle. Its value lies in the result: a knowledge base that keeps improving. The number of people who use that knowledge will always far exceed the number who help build it.
A wiki is also more durable as a form of accumulation. BBSes and blogs mainly accumulate users, and users are easy to lose, which affects momentum and traffic. A wiki mainly accumulates entries. Because of that, it can develop more steadily and maintain a more reliable long-term growth in readership.
Why online media should care about wiki
For online media organizations, a wiki may bring fewer directly registered users than a BBS or a blog. But the knowledge base a wiki can build is a resource many web publishers have long wanted and rarely managed to obtain.
In theory, an online publication can archive everything it publishes. In practice, however, content produced through CMS platforms, blogs, and discussion boards is difficult to revise and difficult to connect meaningfully. The result is often a pile of search results dumped in front of the reader, who has to sort through the mess alone.
A wiki-style knowledge base is different. It is structured, interconnected, and open to continual updating and improvement. That makes it especially suitable for media organizations that want to build a real body of reference knowledge. Compared with traditional media, this is one of online media’s major structural advantages.
A practical way to start is to create a wiki project around the publication’s core subject area, then subdivide it according to existing channels or sections. An IT portal, for example, might begin with an IT encyclopedia and divide it into software, hardware, networking, digital devices, telecommunications, and so on. Those sections can be gathered on the main wiki homepage, while the strongest or newest entries can also appear throughout the site’s content channels.
Because wiki entries often take the form of compact keyword-based pages, they are easy to pull into relevant sections and even embed alongside article pages, increasing their visibility and usefulness.
In such a model, the editors of each channel naturally become the first group of administrators and the main early contributors. But once readers begin participating, the structure can become broader, more complete, and more detailed. The power of readers should never be underestimated: compared with the limited number of editors, they are effectively innumerable. Time should not be underestimated either. A short-term task ends quickly; accumulation through time has no fixed limit.