Jump To Navigation Jump To Search: This Article Is About The Type of Website. For Other Uses, See
Jump To Navigation Jump To Search: This Article Is About The Type of Website. For Other Uses, See
Contents
1Characteristics
o 1.1Editing
1.1.1Navigation
1.1.2Consistency
1.1.3Basic syntax
1.1.4Visual editing
1.1.5Version history
1.1.6Edit summary
o 1.2Navigation
o 1.3Linking and creating pages
o 1.4Searching
2History
3Alternative definitions
4Implementations
5Trust and security
o 5.1Controlling changes
o 5.2Trustworthiness and reliability of content
o 5.3Security
5.3.1Potential malware vector
6Communities
o 6.1Applications
o 6.2City wikis
o 6.3WikiNodes
o 6.4Participants
o 6.5Growth factors
7Conferences
8Rules
9Legal environment
10See also
11Notes
12References
13Further reading
14External links
Characteristics
This section needs additional citations for verification. Please
help improve this article by adding citations to reliable sources.
Unsourced material may be challenged and removed. (March
2017) (Learn how and when to remove this template message)
Ward Cunningham and co-author Bo Leuf, in their book The Wiki Way: Quick Collaboration on
the Web, described the essence of the Wiki concept as follows: [8]
A wiki invites all users—not just experts—to edit any page or to create new pages within
the wiki Web site, using only a standard "plain-vanilla" Web browser without any extra add-
ons.
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.
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.
A wiki enables communities of editors and contributors to write documents collaboratively. All
that people require to contribute is a computer, Internet access, a web browser, and a basic
understanding of a simple markup language (e.g., MediaWiki markup language). A single page in
a wiki website is referred to as a "wiki page", while the entire collection of pages, which are
usually well-interconnected by hyperlinks, is "the wiki". A wiki is essentially a database for
creating, browsing, and searching through information. A wiki allows non-linear, evolving,
complex, and networked text, while also allowing for editor argument, debate, and interaction
regarding the content and formatting. [9] A defining characteristic of wiki technology is the ease
with which pages can be created and updated. Generally, there is no review by a moderator or
gatekeeper before modifications are accepted and thus lead to changes on the website. Many
wikis are open to alteration by the general public without requiring registration of user accounts.
Many edits can be made in real-time and appear almost instantly online, but this feature
facilitates abuse of the system. Private wiki servers require user authentication to edit pages, and
sometimes even to read them. Maged N. Kamel Boulos, Cito Maramba, and Steve Wheeler write
that the open wikis produce a process of Social Darwinism. "... because of the openness and
rapidity that wiki pages can be edited, the pages undergo an evolutionary selection process not
unlike that which nature subjects to living organisms. 'Unfit' sentences and sections are ruthlessly
culled, edited and replaced if they are not considered 'fit', which hopefully results in the evolution
of a higher quality and more relevant page."[10]
Editing
For the project page on editing Wikitext on Wikipedia, see Help:Wikitext.
Wikitext
Cheatsheet
All Wikitext
Magic links
Visual files
Sound files
Tables
Using templates
Wikitext
v
t
e
Navigation
Some wikis have an Edit button or link directly on the page being viewed, if the user has
permission to edit the page. This can lead to a text-based editing page where participants can
structure and format wiki pages with a simplified markup language, sometimes known
as Wikitext, Wiki markup or Wikicode (it can also lead to a WYSIWYG editing page; see the
paragraph after the table below). For example, starting lines of text with asterisks could create
a bulleted list. The style and syntax of wikitexts can vary greatly among wiki implementations,
[example needed]
some of which also allow HTML tags.
Consistency
Wikis have favoured plain-text editing, with fewer and simpler conventions than HTML, for
indicating style and structure. Although limiting access to HTML and Cascading Style
Sheets (CSS) of wikis limits user ability to alter the structure and formatting of wiki content, there
are some benefits. Limited access to CSS promotes consistency in the look and feel, and
having JavaScript disabled prevents a user from implementing code that may limit other users'
access.
Basic syntax
MediaWiki syntax (the
Equivalent HTML (another type of Rendered output
"behind the scenes" code
"behind the scenes" code used to (seen onscreen by a
used to add formatting to
add formatting to text) regular web user)
text)
Visual editing
Wikis can also make WYSIWYG editing available to users, usually by means of JavaScript
control that translates graphically entered formatting instructions into the corresponding HTML
tags or wikitext. In those implementations, the markup of a newly edited, marked-up version of
the page is generated and submitted to the server transparently, shielding the user from this
technical detail. An example of this is the VisualEditor on Wikipedia. WYSIWYG controls do not,
however, always provide all of the features available in wikitext, and some users prefer not to use
a WYSIWYG editor. Hence, many of these sites offer some means to edit the wikitext directly.
Version history
Some wikis keep a record of changes made to wiki pages; often, every version of the page is
stored. This means that authors can revert to an older version of the page should it be necessary
because a mistake has been made, such as the content accidentally being deleted or the page
has been vandalized to include offensive or malicious text or other inappropriate content.
Edit summary
Many wiki implementations, such as MediaWiki, the software that powers Wikipedia, allow users
to supply an edit summary when they edit a page. This is a short piece of text summarizing the
changes they have made (e.g., "Corrected grammar," or "Fixed formatting in table."). It is not
inserted into the article's main text, but is stored along with that revision of the page, allowing
users to explain what has been done and why, similar to a log message when making changes in
a revision-control system. This enables other users to see which changes have been made by
whom and why, often in a list of summaries, dates and other short, relevant content, a list which
is called a "log" or "history."
Navigation
Within the text of most pages, there are usually many hypertext links to other pages within the
wiki. This form of non-linear navigation is more "native" to a wiki than structured/formalized
navigation schemes. Users can also create any number of index or table-of-contents pages, with
hierarchical categorization or whatever form of organization they like. These may be challenging
to maintain "by hand", as multiple authors and users may create and delete pages in an ad hoc,
unorganized manner. Wikis can provide one or more ways to categorize or tag pages to support
the maintenance of such index pages. Some wikis, including the original, have a backlink feature,
which displays all pages that link to a given page. It is also typically possible in a wiki to create
links to pages that do not yet exist, as a way to invite others to share what they know about a
subject new to the wiki. Wiki users can typically "tag" pages with categories or keywords, to
make it easier for other users to find the article. For example, a user creating a new article
on cold weather cycling might "tag" this page under the categories of commuting, winter sports
and bicycling. This would make it easier for other users to find the article.
Searching
Most wikis offer at least a title search, and sometimes a full-text search. The scalability of the
search depends on whether the wiki engine uses a database. Some wikis, such as PmWiki,
use flat files.[11] MediaWiki's first versions used flat files, but it was rewritten by Lee Daniel
Crocker in the early 2000s (decade) to be a database application. [citation needed] Indexed database
access is necessary for high speed searches on large wikis. Alternatively, external search
engines such as Google Search can sometimes be used on wikis with limited searching functions
in order to obtain more precise results.
History
Main article: History of wikis
Wiki Wiki Shuttle at Honolulu International Airport
Alternative definitions
In the late 1990s and early 2000s, the word "wiki" was used to refer to both user-editable
websites and the software that powers them; the latter definition is still occasionally in use. [1] Wiki
inventor Ward Cunningham wrote in 2014 [18] that the word "wiki" should not be used to refer to a
single website, but rather to a mass of user-editable pages or sites so that a single website is not
"a wiki" but "an instance of wiki". He wrote that the concept of wiki federation, in which the same
content can be hosted and edited in more than one location in a manner similar to distributed
version control, meant that the concept of a single discrete "wiki" no longer made sense. [19]
Implementations
See also: List of wiki software
Wiki software is a type of collaborative software that runs a wiki system, allowing web pages to
be created and edited using a common web browser. It may be implemented as a series of
scripts behind an existing web server, or as a standalone application server that runs on one or
more web servers. The content is stored in a file system, and changes to the content are stored
in a relational database management system. A commonly implemented software package
is MediaWiki, which runs Wikipedia. Alternatively, personal wikis run as a standalone application
on a single computer.
Wikis can also be created on a "wiki farm", where the server-side software is implemented by the
wiki farm owner. Some wiki farms can also make private, password-protected wikis. Free wiki
farms generally contain advertising on every page. For more information, see Comparison of wiki
farms.
History comparison reports highlight the changes between two revisions of a page.
Wikis are generally designed with the philosophy of making it easy to correct mistakes, rather
than making it difficult to make them. Thus, while wikis are very open, they provide a means to
verify the validity of recent additions to the body of pages. The most prominent, on almost every
wiki, is the "Recent Changes" page—a specific list numbering recent edits, or a list of edits made
within a given time frame.[20] Some wikis can filter the list to remove minor edits and edits made
by automatic importing scripts ("bots").[21] From the change log, other functions are accessible in
most wikis: the revision history shows previous page versions and the diff feature highlights the
changes between two revisions. Using the revision history, an editor can view and restore a
previous version of the article. This gives great power to the author to eliminate edits. The diff
feature can be used to decide whether or not this is necessary. A regular wiki user can view the
diff of an edit listed on the "Recent Changes" page and, if it is an unacceptable edit, consult the
history, restoring a previous revision; this process is more or less streamlined, depending on the
wiki software used.[22]
In case unacceptable edits are missed on the "recent changes" page, some wiki engines provide
additional content control. It can be monitored to ensure that a page, or a set of pages, keeps its
quality. A person willing to maintain pages will be warned of modifications to the pages, allowing
them to verify the validity of new editions quickly. This can be seen as a very pro-author and anti-
editor feature.[23] A watchlist is a common implementation of this. Some wikis also implement
"patrolled revisions", in which editors with the requisite credentials can mark some edits as not
vandalism. A "flagged revisions" system can prevent edits from going live until they have been
reviewed.[24]