343
343
343
While wiki engines have traditionally offered source editing to users, in recent
years some implementations have added a rich text editing mode. This is usually
implemented, using JavaScript, as an interface which translates formatting
instructions chosen from a toolbar into the corresponding wiki markup or HTML. This
is generated and submitted to the server transparently, shielding users from the
technical detail of markup editing and making it easier for them to change the
content of pages. An example of such an interface is the VisualEditor in MediaWiki,
the wiki engine used by Wikipedia. WYSIWYG editors may not provide all the features
available in wiki markup, and some users prefer not to use them, so a source editor
will often be available simultaneously.
Version history
Some wiki implementations keep a record of changes made to wiki pages, and may
store every version of the page permanently. This allows authors to revert a page
to an older version to rectify a mistake, or counteract a malicious or
inappropriate edit to its content.[13]
These stores are typically presented for each page in a list, called a "log" or
"edit history", available from the page via a link in the interface. The list
displays metadata for each revision to the page, such as the time and date of when
it was stored, and the name of the person who created it, alongside a link to view
that specific revision. A diff (short for "difference") feature may be available,
which highlights the changes between any two revisions.
Edit summaries
"Edit summary" redirects here. For the Wikipedia help page, see Help:Edit summary.
The edit history view in many wiki implementations will include edit summaries
written by users when submitting changes to a page. Similar to the function of a
log message in a revision control system, an edit summary is a short piece of text
which summarizes and perhaps explains the change, for example "Corrected grammar"
or "Fixed table formatting to not extend past page width". It is not inserted into
the article's main text.
Navigation
Traditionally, wikis offer free navigation between their pages via hypertext links
in page text, rather than requiring users to follow a formal or structured
navigation scheme. Users may also create indexes or table of contents pages,
hierarchical categorization via a taxonomy, or other forms of ad hoc content
organization. Wiki implementations can provide one or more ways to categorize or
tag pages to support the maintenance of such index pages, such as a backlink
feature which displays all pages that link to a given page. Adding categories or
tags to a page makes it easier for other users to find it.
Most wikis allow the titles of pages to be searched amongst, and some offer full
text search of all stored content.
While this system made it easy to link to pages, it had the downside of requiring
pages to be named in a form deviating from standard spelling, and titles of a
single word required abnormally capitalizing one of the letters (e.g. "WiKi"
instead of "Wiki"). Some wiki implementations attempt to improve the display of
camel case page titles and links by reinserting spaces and possibly also reverting
to lower case, but this simplistic method is not able to correctly present titles
of mixed capitalization. For example, "Kingdom of France" as a page title would be
written as "KingdomOfFrance", and displayed as "Kingdom Of France".
To avoid this problem, the syntax of wiki markup gained free links, wherein a term
in natural language could be wrapped in special characters to turn it into a link
without modifying it. The concept was given the name in its first implementation,
in UseModWiki in February 2001.[16] In that implementation, link terms were wrapped
in a double set of square brackets, for example [[Kingdom of France]]. This syntax
was adopted by a number of later wiki engines.
It is typically possible for users of a wiki to create links to pages that do not
yet exist, as a way to invite the creation of those pages. Such links are usually
differentiated visually in some fashion, such as being colored red instead of the
default blue, which was the case in the original WikiWikiWeb, or by appearing as a
question mark next to the linked words.
History
Main article: History of wikis
Cunningham's system was inspired by his having used Apple's hypertext software
HyperCard, which allowed users to create interlinked "stacks" of virtual cards.[20]
HyperCard, however, was single-user, and Cunningham was inspired to build upon the
ideas of Vannevar Bush, the inventor of hypertext, by allowing users to "comment on
and change one another's text."[2][21] Cunningham says his goals were to link
together people's experiences to create a new literature to document programming
patterns, and to harness people's natural desire to talk and tell stories with a
technology that would feel comfortable to those not used to "authoring".[20]
By 2014, Ward Cunningham's thinking on the nature of wikis had evolved, leading him
to write[23] 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". In this 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, the idea of a single discrete "wiki"
no longer made sense.[24]
Implementations
See also: List of wiki software
The software which powers a wiki may be implemented as a series of scripts which
operate an existing web server, a standalone application server that runs on one or
more web servers, or in the case of personal wikis, run as a standalone application
on a single computer. Some wikis use flat file databases to store page content,
while others use a relational database,[25] as indexed database access is faster on
large wikis, particularly for searching.
Hosting
See also: Comparison of wiki hosting services
Wikis can also be created on wiki hosting services (also known as wiki farms),
where the server-side software is implemented by the wiki farm owner, and may do so
at no charge in exchange for advertisements being displayed on the wiki's pages.
Some hosting services offer private, password-protected wikis requiring
authentication to access. Free wiki farms generally contain advertising on every
page.