A wiki is a website or information system designed for the collaborative creation, organization, and revision of interlinked pages. Users typically edit content through a web browser, without separately preparing and uploading files. Wiki software commonly provides page histories, comparisons between revisions, and tools for restoring earlier versions. Participation may be open to the public or restricted to an authorized group. Wikipedia is a prominent example, but wikis also support internal documentation, research, education, and community projects.
The word wiki can refer to a particular site, the software that operates it, or the collaborative publishing approach. A wiki is not necessarily an encyclopedia, publicly editable, or freely licensed.
Origins and development
The first wiki, WikiWikiWeb, was created by Ward Cunningham and made publicly available on March 25, 1995. It supported discussion and exchange of ideas about programming and software engineering. Its name comes from the Hawaiian word wiki, meaning “quick”; Cunningham drew inspiration from the name of Honolulu airport’s Wiki Wiki shuttle service.
Early wiki design emphasized a short path between reading and writing. Readers could follow links, edit a page, and create connections to other pages without using a conventional website-publishing workflow. Some early systems recognized links through CamelCase: words written with internal capitals, such as WikiWikiWeb, automatically became page names or links.
Wikipedia, launched in January 2001, brought the wiki approach to large-scale encyclopedia production. Its growth demonstrated that persistent pages, accessible editing tools, revision histories, and community rules could support a substantial collaborative reference work. The model also spread to software projects, businesses, educational institutions, and specialist communities.
Later developments included visual editors, richer access controls, extensions for structured information, and integration with other collaboration tools. Wiki-like editing also became a feature of broader document and workplace platforms, making the boundary between a wiki and other collaborative systems less distinct.
Core characteristics
There is no single technical specification that every wiki must follow. Most share several characteristics.
Editable, interlinked pages
A wiki organizes information into named pages connected by hypertext links. Contributors can usually edit an existing page directly and create new pages through links or a page-creation interface.
Many systems make it easy to link to a page that does not yet exist. Such a link can serve both as navigation and as an invitation to create missing content. This supports incremental development: a subject can be named before it receives a full explanation.
Low-friction authoring
Traditional web publishing may require separate authoring software, file uploads, or an approval process before changes appear. Wikis generally reduce these steps.
Editors may use lightweight markup, a visual editor, or both. Wiki markup commonly provides compact notation for headings, lists, tables, and internal links. Some systems use Markdown, while others use their own syntax. The software converts the stored content into HTML for display.
Ease of editing does not imply unrestricted publication. A wiki may require an account, limit editing to particular groups, or hold changes for review.
Revision history
Most wiki systems retain successive versions of a page. A history commonly records the time of a change, its author or account, and an optional edit summary. A comparison view, often called a diff, shows differences between revisions.
These features provide a form of version control focused on documents. They allow contributors to inspect how a page developed, identify changes, and restore earlier content. The mechanisms are usually simpler than the branching and merging workflows used for source code, although some wikis store their pages in systems such as Git.
A revision history records changes; it does not establish that those changes are accurate. It is also not necessarily an immutable audit record: administrators may be able to delete revisions or restrict access to them.
Collective maintenance
Wiki content is usually treated as a shared, revisable resource rather than a sequence of individually owned publications. Contributors can correct, reorganize, or extend material written by others.
Supporting tools may include recent-change lists, watchlists, notifications, discussion pages, and backlinks showing which pages link to a given page. These help participants coordinate work and detect changes that need attention.
Technical organization
A conventional wiki application receives browser requests, retrieves page content, processes markup or document data, and returns a rendered page. Content and revision information may be stored in a database, ordinary files, or a version-control repository.
Typical components include:
- Page storage: current content, previous revisions, attachments, and page identifiers.
- Rendering: conversion of markup or structured document content into the displayed page.
- Link management: handling page titles, redirects, missing pages, and incoming links.
- Search: finding pages by title or text, sometimes using a separate search engine.
- User and permission management: identifying contributors and determining which actions they may perform.
- Extensions and integration: adding templates, forms, diagrams, import tools, or connections through an application programming interface.
MediaWiki, the software used by Wikipedia, is a widely deployed wiki engine. Other systems differ in their storage models, editing interfaces, permission structures, and intended audiences. Some are distributed as open-source software; others are proprietary products or hosted services.
Edit conflicts and simultaneous editing
Traditional wikis often use an edit–save model. A contributor opens a revision, makes changes, and submits a replacement. If another contributor has changed the page in the meantime, the system may merge compatible changes or report an edit conflict requiring manual resolution.
This differs from real-time collaborative editing, in which participants see one another’s changes while typing. A wiki can support either approach. Real-time editing is not a defining requirement.
Structured and semantic content
A basic wiki primarily stores documents. Templates, categories, forms, and typed fields can add more consistent organization. A semantic wiki goes further by representing explicit relationships or properties that can be queried.
For example, a page about a building might identify its architect, location, and construction date as structured values rather than only as prose. Such features can connect document-oriented collaboration with databases and knowledge graphs, although the level of structure varies considerably between systems.
Participation and governance
A wiki’s technical openness and its social rules are separate matters. Public readability does not necessarily imply public editability, and permission to edit does not necessarily include permission to change every page.
Common arrangements include:
- Public collaborative wikis, where a broad audience can contribute.
- Account-based community wikis, where editing requires registration or membership.
- Organizational wikis, restricted to employees, partners, or project participants.
- Personal wikis, maintained mainly by one person for notes and reference.
Communities may establish rules about reliable evidence, page naming, acceptable behavior, editorial review, and dispute resolution. Administrators may have technical powers to protect pages, block accounts, or remove content, but those powers do not inherently confer subject-matter authority.
Open editing can permit rapid correction and broad participation, but it can also enable vandalism, promotional material, and repeated reversions between opposing contributors, often called edit wars. Registration requirements, page protection, review queues, and automated detection can reduce some forms of abuse, while also increasing barriers to legitimate contribution.
Uses and distinctions from related systems
Wikis are useful when information needs continuing revision by multiple contributors rather than publication as a finished, fixed document.
Common uses include:
- Reference works: encyclopedias, glossaries, and specialist directories.
- Technical documentation: installation instructions, troubleshooting guides, and software documentation.
- Organizational knowledge: internal procedures, project records, and shared knowledge bases.
- Education and research: collaborative assignments, research notes, and collections of disciplinary resources.
- Community projects: documentation of games, local history, hobbies, and cultural subjects.
A wiki differs from a discussion forum mainly in its emphasis on revising shared pages rather than preserving a sequence of messages. A blog generally emphasizes dated posts and identifiable authorship. A conventional content management system may prioritize controlled publishing workflows, whereas a wiki usually emphasizes direct, incremental editing. These distinctions describe typical designs rather than rigid boundaries; individual platforms may combine all these functions.
Reliability, security, and rights
Information quality and maintenance
Wiki software does not guarantee factual accuracy. Quality depends on contributor expertise, source requirements, review practices, and sustained maintenance. Openness can help expose errors, but inaccurate information can persist where few knowledgeable people review it.
Wikis can also accumulate duplicated pages, inconsistent terminology, outdated instructions, and abandoned discussions. Search and extensive linking help users navigate, but they do not replace editorial organization. Internal documentation is especially vulnerable to becoming obsolete when maintenance responsibilities are unclear.
Collaborative authorship can make responsibility harder to identify. A page may combine contributions from many people, while a particular revision may reflect only one editor’s changes. Dates, revision histories, and review labels therefore provide context, not automatic assurance of reliability.
Security and privacy
Wiki systems face the usual risks of web applications, including compromised accounts, unsafe extensions, and inappropriate access permissions. Authentication identifies users, while authorization determines which pages and actions they may access.
Revision retention creates a particular privacy concern: removing sensitive information from the visible page may leave it available in earlier revisions, attachments, search indexes, or backups. Permission design must therefore account for more than the current page view.
Likewise, revision history is not a substitute for data backup. A storage failure or destructive administrative action may affect both current pages and their histories.
Copyright and licensing
Collaborative editing does not eliminate intellectual property rights. A wiki may use an open-content license, reserve rights to an organization, or operate under other contribution terms. Permission to edit a site does not by itself grant permission to republish its contents elsewhere.
Licensing also affects whether material can be imported from another source and how contributors must be credited. Text, photographs, diagrams, and uploaded documents may carry different terms even when they appear on the same wiki.