Wiki

Type of website edited collaboratively

This article is about the concept. For its use as a nickname, one might stumble upon Wikipedia . For other uses, because apparently, the universe wasn’t confusing enough, consult Wiki (disambiguation) .

• And for those truly committed to misdirection, it’s certainly not to be confused with Wiiki or WIKY . One wonders how many times these distinctions had to be made before they were deemed worthy of a formal warning.

Editing display showing MediaWiki markup language A photo of the MediaWiki homepage, a wiki software

A wiki (/ˈwɪki/ ⓘ WICK-ee) represents a rather curious form of hypertext publication, residing on the vast and often chaotic expanse of the internet . Its defining characteristic, the one that sets it apart from more traditional digital tomes, is its profoundly collaborative editing model. This isn’t a one-person show; it’s a digital commune, where the audience itself is invited—or perhaps, permitted—to directly manage and modify its content through the ubiquitous interface of a web browser . Generally, a typical wiki isn’t a singular, isolated document but rather a sprawling collection of multiple interconnected pages. These pages can be either openly editable by the general public, a testament to the enduring, if sometimes misguided, faith in collective intelligence, or they can be restricted for internal organizational use, serving as a private knowledge base . The very name, “wiki,” carries a rather charmingly pragmatic origin story, deriving from the very first user-editable website, the now-legendary WikiWikiWeb . The term “wiki” itself (pronounced [wiki] [note 1]) is a Hawaiian word, meaning ‘quick.’ A fitting moniker, one might concede, given its core promise of rapid content creation and modification. [1] [2] [3] [4]

These collaborative digital spaces, these wikis, are fundamentally powered by specialized wiki software , often referred to with a slightly more technical flourish as wiki engines. While they certainly fall under the broad umbrella of a content management system (CMS), their operational philosophy diverges significantly from other web-based systems. Unlike the often singular vision of blog software or the meticulously pre-rendered output of static site generators , wikis are designed with the somewhat radical premise that content creation should occur without any single, predefined owner or leader. This inherent lack of a rigid, top-down structure is, in fact, one of their greatest strengths, allowing an organic, emergent organization to take shape, dictated entirely by the evolving needs and collective wisdom—or sometimes, folly—of its users. [5] Most wiki engines facilitate content creation through the use of a remarkably accessible lightweight markup language , a simplified syntax that allows users to format text without needing to master the arcane arts of HTML. Increasingly, however, many also offer the convenience of a rich-text editor , attempting to bridge the gap for those who prefer a more visual, less code-centric approach. [6] A quick glance across the digital landscape reveals dozens of distinct wiki engines in active use, some operating as standalone platforms, others seamlessly integrated as components within larger software ecosystems, such as bug tracking systems . The philosophical divide extends even to their licensing: some wiki engines proudly embrace the ethos of free and open-source development, while others remain firmly within the realm of proprietary offerings. Furthermore, the degree of control they offer over various functions, particularly access levels, can vary wildly. For instance, editing rights might be meticulously segmented, permitting certain users to change, add, or remove material, while others might grant unfettered access, trusting in the collective to self-regulate. Beyond the mere mechanics of content modification, wikis also often impose supplementary rules, designed to bring some semblance of order to the vast and ever-growing sea of information. Crucially, in addition to simply hosting content authored by users, wikis actively encourage and facilitate interaction, fostering environments where discussions can flourish, and genuine collaboration can take root. [7]

Today, the sheer number of wikis in use is staggering, numbering in the hundreds of thousands, encompassing both fiercely public platforms and tightly guarded private enclaves. Their applications are incredibly diverse, ranging from vital knowledge management resources within corporations, to indispensable note-taking tools for individuals, vibrant community websites fostering shared interests, and the often-underappreciated backbone of many organizational intranets . Ward Cunningham , the visionary developer credited with creating the very first wiki software, WikiWikiWeb , encapsulated its elegant simplicity when he originally described a wiki as “the simplest online database that could possibly work.” A statement that, in its understated brilliance, perfectly captures the core utility of these platforms. [8]

Without a doubt, the colossal online encyclopedia project, Wikipedia , stands as the undisputed titan among wiki-based websites. It is not merely the most popular wiki-driven platform, but also consistently ranks as one of the internet’s most popular websites , a position it has maintained with unwavering tenacity since at least 2007. [9] What many might not immediately grasp is that Wikipedia itself isn’t a singular, monolithic wiki, but rather a vast constellation of hundreds of independent wikis, each dedicated to a specific language. This distributed, multi-lingual architecture allows it to collectively form the largest reference work ever conceived by humanity. [10] The English-language Wikipedia , naturally, boasts the most extensive collection of articles, a staggering 7,109,584 entries as of December 2025. [11] A truly impressive, if somewhat overwhelming, testament to collaborative effort.

Characteristics

Ward Cunningham

In their seminal 2001 work, The Wiki Way: Quick Collaboration on the Web , Ward Cunningham and his astute co-author, Bo Leuf , distilled the very essence of the wiki concept into a few foundational principles. These aren’t just technical specifications; they are a manifesto for digital collaboration, outlining the core philosophy that makes a wiki, well, a wiki. [12] [13]

• “A wiki invites all users—not just experts—to edit any page or to create new pages within the wiki website, using only a standard ‘plain-vanilla’ Web browser without any extra add-ons .” This point emphasizes the democratized nature of content creation. It’s an open invitation, a challenge to the traditional gatekeepers of information. The barrier to entry is intentionally kept as low as possible, requiring nothing more exotic than the web browser you’re likely using right now. No specialized software, no arcane commands, just the fundamental tools of the internet. This accessibility is crucial; it empowers the broadest possible audience to contribute, fostering a truly collective intelligence, even if that intelligence occasionally veers into the questionable. The notion that “not just experts” are invited is particularly revolutionary, leveling the playing field and valuing collective experience over individual credentials.

• “Wiki promotes meaningful topic associations between different pages by making page link creation intuitively easy and showing whether an intended target page exists or not.” This principle highlights the interconnectedness that defines a wiki. It’s not a collection of isolated documents, but a dense web of information where every piece can, and often does, relate to another. The ease of creating these internal links is paramount; it encourages users to build a rich, navigable structure, rather than a flat, linear one. The immediate feedback — knowing whether a linked page already exists or if you’re forging a path to new knowledge — streamlines the process and encourages expansion, making the wiki grow organically like some digital coral reef.

• “A wiki is not a carefully crafted site created by experts and professional writers and designed for casual visitors. Instead, it seeks to involve the typical visitor/user in an ongoing process of creation and collaboration that constantly changes the website landscape.” This is the core distinction from traditional publishing. A wiki is a living, breathing entity, perpetually in flux. It rejects the static, polished facade of expert-curated content in favor of a dynamic, evolving landscape shaped by its users. It’s a testament to the idea that knowledge is not a fixed monument, but a constantly negotiated and refined process. This continuous cycle of creation and collaboration means the website is never truly “finished,” always adapting, always growing, much like the relentless march of time itself. It invites participation, turning passive consumption into active contribution, for better or worse.

Editing

• “Wikitext” redirects here. For the Wikipedia help page, see Help:Wikitext . A page that, I assure you, is far more useful than many of the things people choose to document.

Source editing

Some wikis, in a nod to their purist roots, will present users with an unambiguous edit button or a direct link, typically positioned right on the page being viewed. Activating this unassuming control opens an interface specifically designed for the intricate task of writing, formatting, and structuring page content. This interface often takes the form of a source editor, a text-based environment where users engage directly with a lightweight markup language. This language, a simplified syntax known variously as wikitext, wiki markup, or wikicode, allows for formatting without the verbose complexity of full HTML. For example, the simple act of starting lines of text with asterisks can, with satisfying efficiency, transform them into a neatly organized bulleted list . It’s a system that values function over ostentation.

The specific syntax and the array of features offered by these wiki markup languages, governing everything from text style to structural elements, can diverge quite significantly across various implementations . Some are remarkably permissive, allowing the integration of raw HTML Tooltip Hypertext Markup Language and CSS Tooltip Cascading Style Sheets, offering a degree of customization that can be both powerful and, in less disciplined hands, utterly chaotic. [14] Conversely, other wiki engines deliberately restrict or even outright prevent the use of these external styling languages, a design choice made with the admirable, if sometimes stifling, goal of fostering a uniform and consistent appearance across the entire wiki. Consistency, after all, is the hobgoblin of little minds, but it’s also quite useful in a sprawling collaborative project.

Example of syntax

To illustrate the rather elegant simplicity of wiki markup, consider a brief excerpt from the timeless 1865 novel, Alice’s Adventures in Wonderland , and observe how it transforms through these different renditions:

As you can observe, the wiki markup, with its double brackets for links and apostrophes for emphasis, is designed to be far more human-readable and quicker to type than its verbose HTML counterpart, yet it yields the exact same formatted output. A small mercy for those of us who prefer not to drown in angle brackets.

Visual editing

While the venerable tradition of wiki engines has historically favored the direct, unvarnished experience of source editing for its users, the more recent annals of software development have seen a growing trend towards the integration of a rich text editing mode. This mode, often implemented with the subtle power of JavaScript , manifests as an intuitive interface that seamlessly translates formatting instructions chosen from a convenient toolbar into the appropriate wiki markup or, indeed, raw HTML. This process occurs almost transparently , generated and submitted to the server behind the scenes, effectively shielding users from the often-intimidating technical intricacies of markup editing. The intention, of course, is to lower the barrier to entry, making it significantly easier for a wider audience to modify page content without needing to learn a new syntax. A prime example of such an interface is the VisualEditor found within MediaWiki , the very wiki engine that underpins the colossal edifice of Wikipedia. However, it’s worth noting that these WYSIWYG (What You See Is What You Get) editors, while convenient, don’t always offer the full spectrum of features and granular control available through direct wiki markup. Consequently, some users, particularly those with a preference for precision or a disdain for abstraction, may choose to forgo them entirely. Hence, a source editor will often remain available, existing in parallel to its visual counterpart, offering a choice for different preferences – a rare nod to individual agency in the digital realm.

Version history

A rather indispensable feature, and indeed, a cornerstone of the wiki philosophy, is the diligent record-keeping maintained by many wiki implementations. These systems keep a meticulous ledger of all changes made to wiki pages, often storing every single version of a page permanently. This isn’t merely for archival purposes; it’s a critical safety net. This comprehensive historical record empowers authors to effortlessly revert a page to an older, unblemished version, allowing for the swift rectification of an accidental mistake or, more critically, the undoing of a malicious or inappropriate edit to its content. [15]

These invaluable historical archives are typically presented for each page in a logically ordered list, commonly referred to as a “log” or “edit history.” This list is readily accessible from the page itself, usually via a discreet link within the interface. Each entry in the list is a snippet of metadata pertaining to a specific revision: the precise time and date of its storage, the name—or pseudonym—of the person responsible for its creation, and a convenient link to view that particular revision in isolation. Furthermore, a crucial " diff ” feature (short for “difference”) is often provided, a powerful tool that visually highlights the exact changes between any two selected revisions. This allows for a granular understanding of how a page has evolved, or devolved, over time.

Edit summaries

• “Edit summary” redirects here. For the Wikipedia help page, see Help:Edit_summary . A concept whose importance is often tragically underestimated.

The edit history view, a staple across many wiki implementations, will frequently incorporate brief but informative edit summaries. These are concise notes penned by users when they submit changes to a page. Much like the function of a log message in a revision control system, an edit summary serves as a succinct encapsulation and, ideally, an explanation of the alteration. For instance, a user might enter “Corrected grammar,” a noble pursuit, or “Fixed table formatting to not extend past page width,” a pragmatic one. The critical distinction is that this summary is purely administrative; it is not, and should never be, inserted into the article’s main text. Its value lies in providing context and transparency for other editors and curious observers, allowing them to quickly grasp the nature of a change without needing to delve into a full “diff” comparison.

Navigation

Traditionally, wikis have championed a philosophy of free and unconstrained navigation between their pages. This is primarily achieved through the pervasive use of hypertext links embedded directly within the page text, a design choice that implicitly rejects the imposition of rigid, formal, or structured navigation schemes. Instead of being forced down a predefined path, users are encouraged to explore the interconnected web of knowledge as they see fit. Naturally, users retain the flexibility to construct their own navigational aids, such as creating indexes or table of contents pages. They can also implement hierarchical categorization through a taxonomy system, or devise other forms of ad hoc content organization, adapting the structure to the evolving needs of the content and community. To further support the maintenance and utility of these index pages, wiki implementations often provide one or more mechanisms for categorizing or tagging pages. A particularly useful feature in this regard is the backlink capability, which displays all pages that currently link to a given page, offering a valuable insight into its contextual relevance and reach within the wiki. The act of adding categories or tags to a page is not merely an organizational nicety; it is a critical function that significantly enhances discoverability, making it substantially easier for other users to locate and engage with relevant content.

Furthermore, the vast majority of wikis offer robust search functionalities. While most permit the titles of pages to be searched amongst, providing a quick way to find specific articles, many more advanced implementations extend this capability to offer full text search across all stored content. This allows users to unearth information even if they don’t know the exact page title, effectively turning the entire wiki into a searchable database of collective knowledge.

Navigation between wikis

• “WikiNode” redirects here. For the app for the Apple iPad, see WikiNodes . Because naturally, if you have one wiki, you eventually need to connect it to others. The human urge to categorize and link is relentless.

Visualization of the collaborative work in the German wiki project Mathe für Nicht-Freaks

Some particularly ambitious and interconnected wiki communities have gone a step further, establishing sophisticated navigational networks between themselves. This is achieved through a system ingeniously dubbed WikiNodes. Conceptually, a WikiNode is essentially a dedicated page on one wiki that serves as a descriptive hub, outlining and providing links to other, related wikis. It’s a digital signpost in a vast wilderness of information. Some wikis operate within a more formalized structure of “neighbors” and “delegates.” In this model, a neighbor wiki is typically one that engages with similar content, shares a common thematic interest, or is otherwise deemed relevant enough to warrant a direct connection. A delegate wiki, on the other hand, represents a more intentional arrangement: it’s a wiki that has explicitly agreed to take on the responsibility of hosting or managing certain specific content that might otherwise reside on the originating wiki. [16] In essence, these WikiNode networks function much like the old webrings of the early internet, allowing users to navigate seamlessly from one node to another in pursuit of a wiki that precisely addresses a particular subject or area of interest. It’s an attempt to impose order on a decentralized ecosystem.

Linking to and naming pages

• “wikilink” redirects here. For the Wikipedia linking how-to guide, see Help:Link . A guide that, I suspect, is consulted with varying degrees of enthusiasm.

The syntax employed to construct internal hyperlinks, those crucial arteries connecting the various pages within a wiki, is not universally standardized; it varies considerably between different wiki implementations. In the nascent days of wiki technology, beginning with the pioneering WikiWikiWeb in 1995, the prevailing convention for naming pages relied heavily on camel case . This linguistic style, where words in a phrase are capitalized and all spaces between them are meticulously removed, resulted in titles like “CamelCase” instead of “camel case.” In these early wiki engines, a rather ingenious mechanism was at play: whenever a page was displayed, any instance of a camel case phrase detected within its text was automatically transformed into a direct link to another page bearing that exact same camel case name.

While this automated system undeniably simplified the act of linking to existing pages—requiring little more than typing the page’s title—it came with a significant drawback. It necessitated that pages be named in a format that conspicuously deviated from standard spelling conventions, often jarring to the eye. Furthermore, single-word titles presented a particular challenge, often requiring an unnatural capitalization of one of their letters (e.g., “WiKi” instead of the more conventional “Wiki”). Some wiki implementations attempted to mitigate the visual awkwardness of camel case page titles and their corresponding links by programmatically reinserting spaces and, where appropriate, reverting to lower case. However, this simplistic method proved incapable of correctly rendering titles with more nuanced or mixed capitalization. For example, a page titled “Kingdom of France ” would be internally written as “KingdomOfFrance” and might then be displayed, rather imperfectly, as “Kingdom Of France.” The machine, it seemed, lacked the human touch.

To circumvent these inherent problems and offer a more natural linguistic experience, the syntax of wiki markup evolved to incorporate what became known as “free links.” This innovation allowed a term expressed in natural language to be enclosed within specific special characters, thereby transforming it into a functional link without necessitating any modification to the term itself. The concept was christened “free links” in its inaugural implementation within UseModWiki in February 2001. [18] In that particular implementation, the terms intended for linking were gracefully wrapped in a double set of square brackets, as exemplified by [[Kingdom of France]]. This more intuitive and less orthographically demanding syntax was subsequently adopted by a multitude of later wiki engines, becoming a widely recognized and appreciated standard.

A particularly forward-thinking aspect of wiki design is the typical allowance for users to create links to pages that, at the moment of creation, do not yet exist. This isn’t an oversight; it’s a deliberate invitation, a subtle prompt for the community to bring those nascent pages into being. To visually distinguish these placeholders from fully fleshed-out articles, such links are usually rendered in a distinct manner. For instance, in the original WikiWikiWeb , they appeared in a striking red, contrasting with the default blue of existing links. Other implementations might employ a simple question mark positioned next to the linked words, serving as a clear indicator of unfulfilled potential. It’s a mechanism that encourages growth and highlights areas where content is needed, a constant reminder of work yet to be done.

History

• Main article: History of wikis Because even the simplest concepts have a lineage, however brief.

Wiki Wiki Shuttle at Honolulu International Airport

The very first instance of what we now recognize as a wiki was the groundbreaking WikiWikiWeb . [19] Its genesis can be traced back to the innovative mind of Ward Cunningham, who commenced its development in 1994. The software was subsequently deployed on the Internet domain c2.com on a pivotal day, March 25, 1995. Cunningham, with a blend of serendipity and linguistic appreciation, bestowed upon it the name “WikiWikiWeb” after a memorable encounter at Honolulu International Airport . A counter employee, in an act of helpful brevity, instructed him to take the " Wiki Wiki Shuttle " bus, which efficiently ferried passengers between the airport’s various terminals. Cunningham later recounted his rationale, observing that “I chose wiki-wiki as an alliterative substitute for ‘quick’ and thereby avoided naming this stuff quick-web.” [20] [21] A decision, one might argue, that inadvertently shaped the very lexicon of the digital age.

Cunningham’s ingenious system found its conceptual roots in his prior experiences with Apple ’s pioneering hypertext software, HyperCard . HyperCard allowed users to meticulously craft interlinked “stacks” of virtual cards, creating a rudimentary form of non-linear information organization. [22] However, HyperCard was fundamentally a single-user experience, a limitation that spurred Cunningham to build upon the more expansive ideas of Vannevar Bush , often hailed as the visionary inventor of hypertext itself. Cunningham’s ambition was to transcend the individual, enabling users to “comment on and change one another’s text,” thereby unlocking a truly collaborative potential. [6] [23] His stated goals were multifaceted: to weave together people’s disparate experiences, forging a new kind of literature specifically designed to document programming patterns ; and, perhaps more profoundly, to harness humanity’s innate desire to communicate, to share stories, utilizing a technology that would feel inherently comfortable even to those unaccustomed to the formal strictures of “authoring.” [22] A rather optimistic view of human nature, considering some of the internet’s later developments.

The Wikipedia project, an online encyclopedia of unprecedented scale, undeniably ascended to become the most famous wiki site [ clarification needed ] – a rather understated claim, given its global omnipresence. Launched with an almost audacious ambition in January 2001, it swiftly garnered momentum, eventually elbowing its way into the top ten most popular websites globally by 2007. The early 2000s marked a significant period of adoption for wikis, as they increasingly found their niche within enterprise environments, evolving into indispensable collaborative software tools. Their common applications within the corporate sphere included streamlining project communication, acting as dynamic intranets , and serving as living repositories for documentation, initially catering primarily to technical users. Today, it is not uncommon for numerous companies to utilize wikis as their primary collaborative software, often replacing static, outdated intranets with these dynamic platforms. Similarly, educational institutions—schools and universities alike—have embraced wikis as powerful instruments to enhance group learning and foster interactive pedagogical approaches. In a tangible acknowledgment of its growing cultural significance, on March 15, 2007, the very word “wiki” was officially enshrined in the online edition of the esteemed Oxford English Dictionary . [24] A quiet triumph for collaborative chaos.

Alternative definitions

In the foundational period of wikis, spanning the late 1990s and the early 2000s, the term “wiki” was imbued with a dual meaning. It was colloquially employed to refer both to the user-editable websites themselves and, somewhat confusingly, to the underlying software that powered them. This latter definition, though less common now, still occasionally surfaces, a lingering echo of its formative years. [5]

However, by 2014, Ward Cunningham’s perspective on the fundamental nature of wikis had undergone a nuanced evolution. This intellectual shift led him to articulate [25] a more refined understanding: that the word “wiki” should, perhaps, not be confined to describing a single, discrete website. Instead, he proposed that “wiki” should properly refer to the broader mass of user-editable pages or sites, suggesting that a singular website is not, in fact, “a wiki,” but rather “an instance of wiki.” This concept, often termed “wiki federation,” posits a future where the same content is not bound to a single location but can be hosted and edited across multiple sites. This mirrors the distributed, decentralized model found in systems like distributed version control , where content’s origin is less important than its existence and evolution across a network. In this federated vision, the traditional notion of a single, self-contained “wiki” as a distinct entity begins to dissolve, becoming a more fluid and interconnected concept. [26] A rather philosophical distinction, but one with profound implications for the future of digital collaboration.

Implementations

• See also: List of wiki software Because naturally, there’s an exhaustive catalog for everything.

The software that breathes life into a wiki can be deployed in a variety of architectural configurations. It might be implemented as a collection of scripts designed to operate harmoniously within an existing web server environment, leveraging established infrastructure. Alternatively, it could manifest as a standalone application server , a dedicated process running independently on one or more web servers, offering greater control and resource allocation. In the more intimate context of personal wikis , the software can even function as a standalone application, residing and operating entirely on a single local computer, transforming a personal device into a private knowledge hub. Regarding data persistence, some wikis opt for the elegant simplicity of flat file databases to meticulously store their page content. However, for wikis of a larger scale, particularly those grappling with vast quantities of information and requiring efficient retrieval, the more robust and performant choice is often a relational database . This is primarily because indexed database access offers significantly faster performance, especially when it comes to the demanding task of searching through extensive datasets. The choice of implementation often reflects a balance between ease of deployment, scalability, and performance requirements.

Hosting

• See also: Comparison of wiki hosting services Another list, because apparently, choices are a burden.

For those who prefer to delegate the technical intricacies, wikis can also be effortlessly created and managed on specialized wiki hosting services , often colloquially referred to as wiki farms. In this model, the demanding server-side software and its associated infrastructure are expertly handled and maintained by the wiki farm owner. Many of these services offer their hosting at no direct financial charge, typically in exchange for the display of advertisements prominently on the wiki’s pages—a classic internet quid pro quo. Beyond the free, ad-supported tiers, some hosting services cater to more discerning users by offering private, password-protected wikis, which necessitate robust authentication mechanisms for access, ensuring a more controlled and secure environment. It’s generally observed that free wiki farms, as a rule, incorporate advertising on virtually every page, a small price to pay for the convenience of outsourced infrastructure.

Trust and security

Access control

The ecosystem of users participating in wikis can generally be segmented into four fundamental types, each with distinct roles and responsibilities. At the base, we have readers, who simply consume the information, a passive but necessary role. Next are authors, the primary contributors who craft and modify the content. Above them are wiki administrators, individuals entrusted with a broader scope of responsibilities concerning content governance. These administrators, by virtue of their elevated privileges , are granted additional functions, which might include, for example, the ability to prevent edits to specific pages, to irrevocably delete pages, to meticulously alter users’ access rights, or even to decisively block individuals from making further edits. At the apex of this hierarchy are system administrators, the technical custodians responsible for the initial installation and ongoing maintenance of the wiki engine itself, alongside the underlying container web server. Their role is to ensure the entire digital edifice remains stable and functional. [28]

Controlling changes

• “Recent changes” redirects here. For the Wikipedia help page, see Help:Recent_changes . For the recent changes page itself, see Special:RecentChanges . A page that, for the vigilant, is a constant source of both information and mild anxiety.

History comparison reports highlight the changes between two revisions of a page.

Wikis, in their fundamental design, often embrace what is termed a “soft security ” philosophy. This approach prioritizes the ease with which mistakes or harmful alterations can be corrected, rather than attempting to erect impenetrable barriers to prevent them from occurring in the first place. It’s a pragmatic recognition that human error and malicious intent are inevitable. This inherent flexibility allows wikis to maintain a highly open and accessible nature while simultaneously providing robust mechanisms for verifying the validity and integrity of recent additions to the collective body of pages. Most wikis, as a standard feature, offer a “recent changes” page. This dynamic page provides an up-to-the-minute overview, displaying recent edits or a comprehensive list of modifications made within a specified time frame. [29] Advanced implementations often allow users to filter this list, enabling them to exclude edits flagged as “minor” by contributors or those performed by automated bots, thereby focusing on more substantial human-made changes. [30] Furthermore, the invaluable version history feature, as previously discussed, serves as a critical safeguard, enabling harmful changes to be reverted quickly and effortlessly, often with just a few clicks. [15]

Some wiki engines extend their content control capabilities even further, providing features that enable remote monitoring and management of individual pages or entire sets of pages. This is primarily aimed at maintaining a consistent level of quality across the wiki. A user who has committed to maintaining specific pages can subscribe to alerts, being notified of any modifications made to them. This proactive notification system allows them to swiftly verify the validity of new editions, intervening promptly if necessary. [31] Such a feature is almost universally known as a “watchlist,” a digital sentinel guarding against entropy.

Beyond simple monitoring, some wikis implement more rigorous oversight mechanisms, such as “patrolled revisions.” In this system, editors possessing the requisite credentials, often earned through trust and consistent contribution, can officially mark edits as being legitimate and reviewed. A more stringent variant is a “flagged revisions” system, which takes an even more cautious approach: it can prevent edits from going live and becoming publicly visible until they have undergone a formal review and been explicitly approved by a designated editor. [32] These layers of control represent a spectrum of trust, balancing openness with the need for quality assurance.

Wikis, in their pursuit of broad participation, may allow any individual on the web to edit their content without the prerequisite of registering an account on the site first—a practice known as “anonymous editing.” This lowers the barrier to entry to its absolute minimum. Conversely, other wikis may impose registration as a mandatory condition for participation, seeking a greater degree of accountability from their contributors. [33] In implementations where an administrator possesses the authority to restrict editing access for a page or a group of pages to a specific, predefined group of users, they often have the granular option to prevent anonymous editing while simultaneously permitting it for registered users. This allows for a flexible approach to security, tailoring access based on context and trust levels. [34]

Trustworthiness and reliability of content

The very foundation of publicly editable wikis often invites a chorus of critics, who frequently raise valid concerns about their susceptibility to manipulation. They argue that such platforms could be easily tampered with by malicious individuals seeking to inject misinformation or, perhaps more benignly but no less problematically, by well-meaning but unskilled users who inadvertently introduce errors into the content. It’s a legitimate fear that the wisdom of the crowd can sometimes be overshadowed by its collective ignorance. Proponents, however, counter that these issues, while present, are typically caught and rectified with remarkable efficiency by the wiki’s active and engaged community of users. The collective vigilance, they argue, acts as a self-correcting mechanism. [6] [19] In specialized domains, such as medicine and health sciences, the imperative for accuracy is paramount. Here, high editorial standards are often enforced, with users typically expected to cite authoritative sources like peer-reviewed journals or university textbooks. This demand for rigor has spurred the development of “expert-moderated wikis,” where contributions are vetted by verified professionals. [35] Furthermore, the inherent wiki feature of retaining and providing access to specific versions of articles has proven immensely valuable to the scientific community, allowing expert peer reviewers to precisely link to trusted, analyzed versions of articles, ensuring reproducibility and accountability. [36]

Security

• “Edit war” redirects here; not to be confused with Edit conflict . For Wikipedia’s policy on edit warring, see Wikipedia:Edit_warring . A policy, one might note, that is often tested by the sheer obstinacy of human nature.

The open and collaborative nature of wikis, while a strength, also exposes them to various forms of digital malfeasance. Trolling and cybervandalism are persistent scourges, manifesting as content being changed to something deliberately incorrect, the insertion of a hoax , the addition of offensive or nonsensical material, or the malicious removal of legitimate content. On larger wiki sites, with their immense volume of changes, such harmful alterations can unfortunately go unnoticed for extended periods, silently corrupting the knowledge base.

To combat these threats, beyond the inherent “soft security” approach, larger wikis often deploy increasingly sophisticated methods. This includes the use of automated bots designed to automatically identify and revert acts of vandalism. A prime example is Wikipedia’s bot, ClueBot NG, which employs advanced machine learning algorithms to identify likely harmful changes and, with astonishing speed, reverts these alterations within minutes or even mere seconds. [37] Another perennial challenge arises from disagreements between users regarding the content or appearance of pages, which can escalate into “edit wars.” These are characterized by competing users repetitively changing a page back to a version they individually favor, creating a volatile cycle of reversion. In such scenarios, some wiki software empowers administrators to temporarily prevent pages from being editable until a consensus or a decision has been reached on the most appropriate version of the page. [7]

Beyond the internal mechanisms, some wikis operate within external structures of governance. These frameworks, common in academic contexts, address and regulate the behavior of individuals granted access to the system, ensuring adherence to institutional standards and norms. [27]

Harmful external links

As most wikis, in their spirit of interconnectedness, permit the creation of hyperlinks to other sites and external services, the potential for the addition of malicious hyperlinks poses another significant security concern. These could point to sites infected with malware or engage in phishing attempts. For instance, in a notable incident in 2006, a German Wikipedia article concerning the Blaster Worm was illicitly edited to include a hyperlink leading to a malicious website. Users of vulnerable Microsoft Windows systems who, perhaps unwisely, followed this link found their systems subsequently infected with the worm. [7] To counteract such threats, some wiki engines offer a crucial blacklist feature. This functionality prevents users from adding hyperlinks to specific sites that have been identified as problematic and subsequently placed on this restricted list by the wiki’s diligent administrators. It’s a necessary gatekeeping function in an otherwise open system.

Communities

The home page of the English Wikipedia , as of June 24, 2024 A monument to human dedication, or perhaps, obsession.

Applications

The English Wikipedia stands as an unparalleled colossus, boasting the largest user base among all wikis on the sprawling World Wide Web . [38] Its dominance is further underscored by its consistent ranking within the top 10 among all websites globally in terms of traffic, a testament to its ubiquitous influence. [39] Beyond Wikipedia, other notable large wikis include the pioneering WikiWikiWeb itself, the comprehensive Memory Alpha (a treasure trove for Star Trek enthusiasts), the invaluable travel guide Wikivoyage , and the once prominent Swedish-language knowledge base, Susning.nu . The application of wikis extends into specialized domains, such as medical and health-related fields. A prime example is Ganfyd , an online collaborative medical reference resource meticulously edited by verified medical professionals and carefully invited non-medical experts, ensuring the integrity of critical health information. [40] It’s also worth noting that a substantial number of wiki communities operate privately, particularly within the confines of enterprises . These internal wikis are frequently deployed as indispensable documentation hubs for in-house systems and proprietary applications, serving as living manuals for complex organizational knowledge. Furthermore, some forward-thinking companies strategically leverage wikis to empower their customers, inviting them to actively participate in the collaborative production and refinement of software documentation, fostering a sense of shared ownership and improving accuracy. [41] A study delving into the behavior of corporate wiki users revealed an interesting bifurcation: contributors could be broadly categorized into “synthesizers” and “adders” of content. Intriguingly, the frequency of contribution for synthesizers was found to be more significantly influenced by the perceived impact their contributions had on other wiki users, suggesting a social motivation. Conversely, adders’ contribution frequency was more closely tied to their ability to accomplish their immediate work tasks, indicating a more utilitarian drive. [42] Drawing from an extensive analysis of thousands of wiki deployments, Jonathan Grudin concluded that meticulous stakeholder analysis and comprehensive education are absolutely crucial ingredients for the successful and sustainable deployment of enterprise wikis. [43]

In 2005, the prescient Gartner Group, observing the undeniable surge in the popularity of wikis, ventured an estimate that these collaborative platforms would transition from niche tools to mainstream collaboration instruments in at least 50% of companies by 2009. [44] [ needs update ] — an update that, I suspect, would show an even higher adoption rate, given the relentless march of technology. Beyond simple documentation, wikis have proven remarkably versatile, finding significant utility in the realm of project management . [45] [46] [ unreliable source ] Their ability to facilitate shared documentation, task tracking, and iterative planning makes them an ideal digital workspace for collaborative endeavors. Moreover, wikis have been enthusiastically adopted within the academic community, serving as powerful conduits for the sharing and dissemination of information across institutional and even international boundaries. [47] In these scholarly settings, they have proven invaluable for fostering collaboration on complex tasks such as grant writing , developing strategic planning documents, organizing departmental documentation, and streamlining committee work. [48] The mid-2000s witnessed a growing impetus across various industries towards fostering greater collaboration, which in turn placed a heavier responsibility upon educators to equip students with proficiency in collaborative work. This societal shift further fueled an already burgeoning interest in integrating wikis into the classroom as effective pedagogical tools. [7]

Wikis have, perhaps surprisingly, carved out a distinct niche within both the legal profession and governmental sectors, demonstrating their adaptability beyond purely technical or academic realms. Notable examples abound: the Central Intelligence Agency ’s Intellipedia , a secure wiki designed for the collaborative sharing and collection of sensitive intelligence assessments ; DKosopedia , a platform utilized by the American Civil Liberties Union to assist in the meticulous review of documents pertaining to the internment of detainees at Guantánamo Bay ; [49] and the wiki maintained by the United States Court of Appeals for the Seventh Circuit , which serves as a public repository for court rules and, notably, allows legal practitioners to comment and pose questions, fostering a direct dialogue. The United States Patent and Trademark Office operates Peer-to-Patent , an innovative wiki designed to harness the collective intelligence of the public in identifying prior art relevant to the examination of pending patent applications, thereby enhancing the rigor of the patenting process. Even local governance has embraced the wiki model: the borough of Queens , New York, famously employed a wiki to enable its citizens to collaboratively participate in the design and planning of a local park, demonstrating a direct democratic application. However, not all wiki endeavors are without their challenges; Cornell Law School ’s wiki-based legal dictionary, Wex , has seen its growth somewhat hampered by restrictions on who is permitted to edit, highlighting the tension between open collaboration and expert curation. [34]

In more general academic contexts, beyond specific legal or governmental applications, wikis have also proven themselves as highly effective systems for facilitating project collaboration and providing robust research support. [50] [51] Their ability to centralize information, track changes, and allow multiple contributors to work asynchronously makes them invaluable tools in the modern research landscape.

City wikis

A “city wiki” or “local wiki” represents a specialized application of wiki technology, functioning as a localized knowledge base and, in many respects, a social network specifically tailored for a particular geographical locale. [52] [53] [54] The term, while often implying a dense urban area, is sometimes broadened to encompass wikis that cover not just a major city, but also smaller towns or even entire regional areas, adapting its scope to the community it serves. The critical distinction of such a wiki lies in its focus on highly localized, granular information—details that might be too specific or ephemeral for a global encyclopedia but are immensely valuable for residents and visitors alike. This highly localized information, perfectly suited for a wiki targeted at local viewers, could encompass a diverse array of content:

• Details of public establishments: This might include precise information about local public houses, bustling bars, available accommodation options, or vital social centers, offering practical guidance for navigating the local scene.
• Owner names, opening hours, and statistics: For a specific shop, this could involve the proprietor’s name, the exact hours of operation, and even anecdotal or statistical information about its business, painting a vivid picture of local commerce.
• Statistical information about a specific road: This level of detail could include traffic patterns, historical significance, or even local regulations pertaining to a particular thoroughfare within the city, providing hyper-local context.
• Flavors of ice cream served at a local ice cream parlor: A seemingly trivial detail, but one that highlights the wiki’s capacity to capture the unique, lived experience of a place, from the profound to the delightfully mundane.
• A biography of a local mayor and other persons: Providing biographical sketches of prominent local figures, offering insight into the individuals shaping the community.

Growth factors

A comprehensive study conducted in 2008, which meticulously analyzed several hundred wikis, yielded some intriguing insights into the dynamics of their growth. The research indicated that a relatively high number of administrators, when compared to the existing content size, was likely to impede growth; too many cooks, it seems, can indeed spoil the broth. [55] Furthermore, the presence of stringent access controls that restricted editing solely to registered users tended to dampen growth, suggesting that barriers to entry, however well-intentioned, can stifle expansion. Conversely, a noticeable lack of such access controls, allowing for anonymous editing, tended to fuel new user registration, indicating that openness is a potent catalyst for community expansion. Interestingly, the study found that a higher ratio of administrators to regular users had no statistically significant effect on either content or population growth, suggesting that raw numbers of oversight personnel are less impactful than the nature of the access controls themselves. [56]

Legal environment

The collaborative nature of articles, where numerous users participate in the iterative process of correcting, editing, and ultimately compiling the finished product, introduces a complex legal dimension, particularly concerning copyright. This joint authorship can inadvertently lead to editors becoming tenants in common of the copyright. The practical implication of this is profound: it can render republication of the content impossible without first securing explicit permission from all co-owners, a task made exponentially difficult when some of these co-owners’ identities may be obscured by pseudonymous or entirely anonymous editing. [7] This labyrinthine problem, however, can often be mitigated or entirely alleviated through the judicious use of an open content license. Version 2 of the GNU Free Documentation License , for example, includes a specific provision designed for wiki relicensing, acknowledging the unique challenges of collaborative platforms. Similarly, Creative Commons licenses, with their flexible frameworks, are also widely popular choices for wikis seeking to clarify usage rights. In instances where no explicit license is specified, an implied license to read and add content to a wiki may, under certain legal interpretations, be deemed to exist. This implied license is typically predicated on the grounds of business necessity and the inherent, collaborative nature of a wiki itself.

Beyond copyright, wikis and their operators can face legal liability for certain activities that transpire on their platforms. If a wiki owner exhibits clear indifference to infringing activities and deliberately forgoes exercising controls (such as banning repeat copyright infringers) that they demonstrably could have employed to halt copyright infringement, they may be deemed to have authorized the infringement. This is particularly true if the wiki is primarily utilized for infringing copyrights or if it accrues a direct financial benefit, such as advertising revenue, from such illicit activities. [7] In the United States, wikis often benefit from the protective shield of Section 230 of the Communications Decency Act . This crucial legal provision generally protects online platforms that engage in “Good Samaritan ” policing of harmful material, notably without imposing a stringent requirement on the quality or quantity of such self-policing. [57] Conversely, it has also been argued that a wiki’s very enforcement of certain editorial rules—such as policies against bias, demands for verifiability, requirements for reliable sourcing, and prohibitions against original research—could paradoxically pose its own set of legal risks. [58] In cases where defamation occurs on a wiki, the theoretical liability could extend to all users of the wiki, given that any one of them possessed the ability to remove or amend the defamatory material from the “publication.” The legal landscape here remains somewhat unsettled, as it awaits clearer judicial determination on whether wikis will ultimately be regarded as more akin to an internet service provider —which is generally not held liable due to its lack of direct control over content—or a publisher, which bears greater responsibility. [7] Finally, it has been sagely recommended that trademark owners diligently monitor the information presented about their trademarks on wikis. This vigilance is advised because courts may potentially use such content as evidence pertaining to public perceptions of the trademark, and active owners can, crucially, edit entries to rectify any misinformation. [59]

Conferences

For those who find the intricacies of wikis and open collaboration sufficiently compelling to gather in person, a number of specialized conferences and meetings are regularly held.

Active conferences and meetings about wiki-related topics include:

• Atlassian Summit: An annual conference catering specifically to the extensive user base of Atlassian software, which notably includes Confluence , a prominent wiki platform widely adopted in enterprise environments. [60]
• OpenSym: Formerly known as WikiSym until 2014, this is a distinguished academic conference dedicated with scholarly rigor to research pertaining to wikis and the broader field of open collaboration.
• SMWCon: A bi-annual conference that brings together both enthusiastic users and dedicated developers of Semantic MediaWiki , focusing on the integration of structured data within wiki environments. [61]
• TikiFest: A frequently held gathering for the vibrant community of users and developers behind Tiki Wiki CMS Groupware , a comprehensive open-source web application suite. [62]
• Wikimania : The flagship annual conference, wholly dedicated to the extensive research and practical application surrounding projects overseen by the Wikimedia Foundation , with Wikipedia naturally taking center stage.

Former wiki-related events, which have since concluded their run, include:

• RecentChangesCamp (2006–2012): An unconference format event, characterized by its participant-driven agenda, focusing on a wide array of wiki-related topics.
• RegioWikiCamp (2009–2013): A semi-annual unconference specifically centered on “regiowikis,” or wikis dedicated to cities and other defined geographic areas, fostering local knowledge exchange. [63]

See also

• Internet portal

• Comparison of wiki software  – A rather necessary comparison of software used to run collaborative wikis.

• Content management system  – The broader category of software for managing digital content.

• CURIE  – A form of abbreviated URI, for those who appreciate brevity.

• Dispersed knowledge  – Information that is spread throughout the market and not in the hands of a single agent, which wikis rather neatly address.

• Fork and pull model – A common alternate paradigm for collaborative development, often seen alongside wikis.

• List of wikis

• Mass collaboration  – The very essence of many people working on a single project.

• Universal Edit Button  – A browser extension indicating a website is editable, a subtle invitation to contribute.

• Wikis and education

Notes

• ^ The realization of the Hawaiian /w/ phoneme exhibits a degree of variability, fluctuating between the labial-velar approximant [w] and the voiced labiodental fricative [v]. Similarly, the articulation of the /k/ phoneme is not entirely fixed, varying between the voiceless velar stop [k] and the voiceless alveolar stop [t], among other less common realizations. Consequently, the pronunciation of the Hawaiian word wiki itself is not monolithic, but rather encompasses a range of variations, including [‘wiki], [‘witi], [‘viki], and [‘viti]. This linguistic fluidity adds a layer of phonetic complexity to a seemingly simple word. For a more exhaustive exploration of these intricate phonetic distinctions, one might consult the detailed article on Hawaiian phonology .