Contents

WikitextEdit

Wikitext is the markup language used by MediaWiki, the software platform behind many community-driven knowledge projects such as Wikipedia and a broad family of wikis. It is designed to be readable in plain text while providing a compact system for structuring content, citing sources, and reusing common elements across pages. The markup language sits at the core of how contributors organize information, enabling pages to be built from headings, lists, links, templates, and media without requiring a traditional content management workflow. When editors save their edits, the MediaWiki parser converts wikitext into HTML for display on the web.

Because it emphasizes modularity and provenance, wikitext supports a high level of consistency across large repositories. Templates, categories, and parser functions let editors apply standard formats and enforce policy or style across many articles with a single change to a template or a module. This design aims to balance openness with reliability, a priority for projects that depend on long-term trust in their content and its sourcing. The result is a system in which collaboration scales—thousands of pages can be edited coherently by communities without centralized authorship, a pattern familiar to Wikipedia and related communities.

History and scope

Wikitext emerged as the lightweight markup of the MediaWiki platform and has evolved alongside the software. It was conceived to be approachable for volunteers who may not be professional editors, while still offering enough structure to support precise formatting, citation, and cross-linking. Over time, the ecosystem around wikitext expanded to include a rich set of templates and extensions that extend what editors can accomplish without resorting to raw HTML. The collaboration model—contributing to a shared knowledge base with open revision history—depends on this markup being expressive enough for experts and approachable enough for newcomers, and on the ability to audit changes through diffs and discussions. See how MediaWiki and Wikimedia projects manage this balance, and how pages such as Wikipedia rely on the same underlying syntax.

Syntax and constructs

Wikitext provides a compact syntax for a wide range of tasks. The following overview highlights the most common features and their practical uses.

Internal and external links

  • Internal links connect to other pages within the same wiki, typically written as Page Title or Page Title.
  • External links point to sources outside the wiki, written as [https://example.org Display Text].

These linking mechanisms drive the interconnected structure of the encyclopedia, enabling readers to move through related topics with minimal friction. For example, linking from a page about a historical topic to a related person might look like George Washington and Constitution.

Text formatting and emphasis

  • Bold and italics are produced with simple tokens: Bold is '''text''' and italic is ''text''; combined emphasis can be '''''bold italic'''''.
  • Headings are created with equal signs, such as == Section Title == for a primary heading and === Subsection === for a subheading.

Lists and tables

  • Unordered lists use asterisks (*) and ordered lists use hashes (#).
  • Tables use a markup block beginning with {| and ending with |}. Rows and cells are defined with |-, ||, and ! for headers.

Templates and transclusion

  • Templates reuse content across pages, written as {{TemplateName|param=value}}. This mechanism—transclusion—lets editors maintain consistent phrasing, infoboxes, and policy statements at scale.
  • Complex formatting can be embedded through templates that themselves pull data from other templates or modules.

References and citations

  • References are commonly created with tags, and a page may render a compiled list of citations with . This system supports inline citations and bibliography-like sections across articles.

Media and files

  • Images and media are included with markup like File:Example.jpg. This supports various display options, including thumbnails and alignment.

Parser functions and magic words

  • Beyond basic syntax, wikitext relies on a set of parser functions and magic words to produce dynamic content, conditional formatting, and metadata. Examples include functions that compare strings, insert the current date, or reveal page metadata such as {{PAGENAME}} for the current page title. See how Parser functions and related features interact with templates to power consistent pages.

Categories and metadata

  • Tags like Category:History help organize pages into topical groupings, creating navigable index pages and helping readers discover related content.

Extensions and ecosystem

The wikitext experience is augmented by extensions and modules that run in the MediaWiki environment. Some create powerful capabilities without changing the core markup language:

  • Lua modules via the Scribunto extension allow authors to run lightweight scripts that compute values for templates and pages. This combination gives editors a form of lightweight programming to maintain consistency and automate repetitive tasks, while keeping the document markup clean and readable.
  • VisualEditor provides a WYSIWYG editing experience, which some users prefer for lowering barriers to contribution. Proponents argue it broadens participation, while critics say it can obscure the markup and lead to inconsistent formatting over time.
  • Template libraries and pre-built modules make common structures—infoboxes, legal disclaimers, and citation formats—easy to reuse across many pages, supporting a predictable user experience and quicker page creation.
  • Wikidata integration enables structured data to live separately from narrative text, reducing duplication and enabling more precise queries, while still being presented through wikitext-rendered pages on Wikipedia and other projects.

The design philosophy behind such extensions emphasizes openness and efficiency: editors can contribute substantive content with a relatively small set of skills, while experienced editors use templates and modules to safeguard quality and coherence across the wiki network.

Controversies and debates

As with any large, volunteer-driven information project, there are ongoing debates about how best to balance openness, quality, and usability:

  • Complexity vs. participation: Critics argue that the learning curve of wikitext and the reliance on templates can deter casual contributors, potentially slowing the expansion of knowledge in less-traveled topics. Supporters counter that the markup’s structure helps maintain long-term clarity and reliability, which is essential for a reference work of broad reach. The debate often centers on whether the benefits of rigorous formatting and consistent presentational standards outweigh the costs of onboarding new editors.
  • Template bloat and maintainability: The use of templates and transclusion can create powerful, uniform pages, but it can also yield “template spaghetti” or situations where understanding a page requires following many layers of templates and modules. Proponents argue that centralized templates prevent duplicative mistakes and enforce best practices; critics say this can reduce transparency and make edits more error-prone for newcomers.
  • VisualEditor vs. hand editing: The move toward WYSIWYG-style editing tools is seen by some as essential to sustaining participation in large wikis, while others worry about drifting away from the precise control that traditional wikitext provides. In practice, many communities aim to offer both options, allowing editors to choose the approach that fits their skill level and task, while ensuring that the resulting markup remains clean and maintainable.
  • Governance and norms: In expansive projects, editorial norms—regarding sourcing, neutrality, and verifiability—are enforced through community consensus rather than centralized authority. Supporters view this as a robust model for open knowledge that rewards merit and accountability; critics occasionally argue that power effectively rests with a relatively small cadre of long-standing editors who shape norms and limit dissent. Advocates for a pragmatic approach emphasize clear guidelines and transparent discussion to preserve trust while inviting broad participation.

See also