HowItWorks:MediaWiki - Revision history

Rongzhou: /* Try it yourself */

2026-09-01T21:02:46Z

Try it yourself

← Older revision		Revision as of 21:02, 1 September 2026
Line 621:		Line 621:
	Output:		Output:

	<~~syntaxhighlight lang="text" copy~~>		<pre>
	"generator":"MediaWiki 1.46.0"		"generator":"MediaWiki 1.46.0"
	</~~syntaxhighlight~~>		</pre>

	<syntaxhighlight lang="bash" copy>		<syntaxhighlight lang="bash" copy>
Line 632:		Line 632:
	Output:		Output:

	<~~syntaxhighlight lang="text" copy~~>		<pre>
	<p><strong>Hi, welcome to ronzz.ORG's wikibase.		<p><strong>Hi, welcome to ronzz.ORG's wikibase.
	</~~syntaxhighlight~~>		</pre>

	<syntaxhighlight lang="bash" copy>		<syntaxhighlight lang="bash" copy>
Line 643:		Line 643:
	Output:		Output:

	<~~syntaxhighlight lang="text" copy~~>		<pre>
	<b>Bold</b> and <i>italic</i>		<b>Bold</b> and <i>italic</i>
	</~~syntaxhighlight~~>		</pre>

	<syntaxhighlight lang="bash" copy>		<syntaxhighlight lang="bash" copy>
Line 654:		Line 654:
	Output:		Output:

	<~~syntaxhighlight lang="text" copy~~>		<pre>
	"user":"Rongzhou"		"user":"Rongzhou"
	"timestamp":"2026-08-24T14:55:13Z"		"timestamp":"2026-08-24T14:55:13Z"
Line 661:		Line 661:
	"user":"Rongzhou"		"user":"Rongzhou"
	"timestamp":"2026-08-19T18:59:55Z"		"timestamp":"2026-08-19T18:59:55Z"
	</~~syntaxhighlight~~>		</pre>

	See the preprocessor stage directly: Visit {{Special:ExpandTemplates}}		See the preprocessor stage directly: Visit {{Special:ExpandTemplates}}

Rongzhou: /* Try it yourself */

2026-09-01T21:01:13Z

Try it yourself

← Older revision		Revision as of 21:01, 1 September 2026
Line 612:		Line 612:
	== Try it yourself ==		== Try it yourself ==

	All commands below were verified to work at the time of writing (2026-08-28) against this wiki, which runs MediaWiki 1.46.0 ~~(confirmed via the siteinfo API below)~~.		All commands below were verified to work at the time of writing (2026-08-28) against this wiki, which runs MediaWiki 1.46.0.

	<syntaxhighlight lang="bash" copy>		<syntaxhighlight lang="bash" copy>
Line 667:		Line 667:
	* paste <code><nowiki>{{HowItWorks}}</nowiki></code> into the input box and click "Expand" —		* paste <code><nowiki>{{HowItWorks}}</nowiki></code> into the input box and click "Expand" —
	* you see the expanded wikitext, before the parser turns it into HTML.		* you see the expanded wikitext, before the parser turns it into HTML.

	~~'''Verification:''' the outputs above were checked against the live API on 2026-08-28:~~

	* [https://wikibase.ronzz.org/api.php?action=query&meta=siteinfo&siprop=general%7Cextensions&format=json Siteinfo API] — version, PHP and database, extension list
	* [https://wikibase.ronzz.org/api.php?action=parse&page=Main_Page&format=json Parse API for Main Page]
	* [https://wikibase.ronzz.org/api.php?action=parse&text=%27%27%27Bold%27%27%27%20and%20%27%27italic%27%27&prop=text&format=json Parse API with raw text]
	* [https://wikibase.ronzz.org/api.php?action=query&prop=revisions&titles=Main_Page&rvprop=timestamp%7Cuser&rvlimit=3&format=json Revisions query (timestamp\|user)]

	== References ==		== References ==

Rongzhou: /* MediaWiki, a wiki engine */

2026-09-01T08:34:44Z

MediaWiki, a wiki engine

← Older revision		Revision as of 08:34, 1 September 2026
Line 9:		Line 9:
	A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.		A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.

	MediaWiki is one of the most well-known wiki engines. Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become ~~one of the most well-known wiki engines~~.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386~~}}</ref> Today, it is used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378~~}}</ref>		MediaWiki is one of the most well-known wiki engines. Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become what it is today.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref>

	== A short history ==		== A short history ==

Rongzhou: /* MediaWiki, a wiki engine */

2026-09-01T08:32:37Z

MediaWiki, a wiki engine

← Older revision		Revision as of 08:32, 1 September 2026
Line 9:		Line 9:
	A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.		A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.

	MediaWiki, one of the most well-known wiki engines, Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become one of the most well-known wiki engines.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref> Today, it is used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378}}</ref>		MediaWiki is one of the most well-known wiki engines. Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become one of the most well-known wiki engines.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref> Today, it is used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378}}</ref>

	== A short history ==		== A short history ==

Rongzhou: /* A short history */

2026-09-01T08:31:46Z

A short history

← Older revision		Revision as of 08:31, 1 September 2026
Line 13:		Line 13:
	== A short history ==		== A short history ==

	MediaWiki was born as the software behind Wikipedia. When Wikipedia launched in January 2001, it ran on '''UseModWiki''', an existing wiki engine written in Perl that stored every page as a text file — and MediaWiki's markup still descends from it.<ref>{{#cite:Q1377}}</ref> As CamelCase proved unsuitable for naming encyclopedia articles, UseModWiki gained "free links" — the double-square-bracket syntax <code><nowiki>[[…]]</nowiki></code> that ~~still defines links in wikitext today — in late January 2001, the first sign~~ of Wikipedia ~~shaping the software that powered it~~.~~<ref>{{#cite:Q1377}}</ref>~~		The history of MediaWiki was intertwined with that of Wikipedia.

	~~The flat-file storage soon became a performance bottleneck, and~~ in ~~the summer of~~ 2001 ~~[[Person:Heinrich Magnus Manske\|Magnus Manske]]~~, ~~then a university student~~, ~~started building a dedicated~~ engine in ~~his free time:~~ a ~~database-driven application written in PHP, backed by MySQL~~. ~~The community knew it simply as "~~the ~~PHP script", "PHP wiki", or "Phase II".<ref>{{#cite~~:~~Q1377}}</ref> The English Wikipedia switched to~~ it ~~in January 2002.<ref>{{#cite:Q1377}}</ref> As the first iteration of what~~ would ~~become MediaWiki, Phase II already introduced features still in use today: namespaces (including talk pages), skins, and special pages~~.~~<ref>{{#cite:Q1377}}</ref>~~		When Wikipedia launched in January 2001, it ran on '''UseModWiki''', an existing wiki engine written in Perl that stored every page as a text file. This worked fine for Wikipedia's scale at the time: an ambitious but still niche startup project that no one knew if it would ever take off.

	~~Performance problems quickly returned~~, ~~and in 2002~~ [[Person:~~Lee Daniel Crocker~~\|~~Lee Daniel Crocker~~]] ~~rewrote the engine again~~, ~~calling the new software "Phase III". As he later described it~~, ~~there "wasn't much~~ time ~~to sit down and properly architect and develop~~ a ~~solution"~~, ~~so he "just reorganised~~ the ~~existing architecture for better performance~~ and ~~hacked all the code"~~.<ref>{{#cite:Q1377}}</ref> ~~Deployed~~ to the ~~English Wikipedia in July 2002, Phase III added a file upload system, side-by-side diffs, and interwiki links~~.<ref>{{#cite:Q1377}}</ref>		To many people's surprise, Wikipedia became an instant hit. In a few months of time, flat-file storage became a performance bottleneck. To improve performance, [[Person:Heinrich Magnus Manske\|Magnus Manske]], then a university student studying biochemistry, started building a dedicated engine in his free time over the summer of 2001: a database-driven application written in PHP, backed by MySQL. It was the first iteration of what would become MediaWiki, introducing core features still in use today: custom namespaces with dedicated talk pages, skins, and special pages.<ref>{{#cite:Q1377}}</ref> The community referred to it simply as "the PHP script".<ref>{{#cite:Q1377}}</ref>

	In ~~June 2003~~, ~~[[Person:Jimmy Wales\|Jimmy Wales]] created~~ the ~~[[Collective:Wikimedia Foundation\|Wikimedia Foundation]], the non-profit that supports~~ Wikipedia ~~and manages its infrastructure and day-~~to~~-day operations.<ref>{{#cite:Q1377}}</ref> The following month~~, the "Wikipedia ~~software~~" was officially named '''MediaWiki''', a wordplay by [[Person:Daniel Mayer\|Daniel Mayer]] on the Foundation's name.<ref>{{#cite:Q1377}}</ref> The first release under the new name followed in August 2003.<ref>{{#cite:Q1377}}</ref>		In January 2002, the English Wikipedia switched officially to Magnus's PHP script, and the script became known as "Wikipedia phase II".<ref>{{#cite:Q1377}}</ref>

	~~MediaWiki's explosive growth was driven by volunteer developers~~.~~<ref>{{#cite:Q1377}}</ref>~~ [[Person:~~Tim Starling~~\|~~Tim Starling~~]] ~~added '''templates''' in MediaWiki 1~~.~~2 (2004); version 1.3 (August 2004) then expanded them with parameters~~, ~~moved them into~~ a ~~dedicated Template namespace~~, and ~~introduced~~ the ~~MonoBook skin as the new default layout~~.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:~~Q1379~~}}</ref>		As Wikipedia continued to grow at an astronomical pace, performance problems returned in a few months. In 2002, [[Person:Lee Daniel Crocker\|Lee Daniel Crocker]] rewrote the engine again, calling the new software "Phase III". As he later described it, there "wasn't much time to sit down and properly architect and develop a solution", so he "just reorganised the existing architecture for better performance and hacked all the code".<ref>{{#cite:Q1377}}</ref> Deployed to the English Wikipedia in July 2002, Phase III added a file upload system, side-by-side diffs, and interwiki links.<ref>{{#cite:Q1377}}</ref>

	~~Development has continued incrementally and continuously ever since — more than two decades~~ of it ~~— repeatedly reworked to keep up with~~ Wikipedia's ~~scale:~~<ref>{{#cite:Q1377}}</ref> ~~the template preprocessor was rewritten in~~ MediaWiki ~~1.12 (2008)~~,~~<ref>{{#cite~~:~~Q1381}}</ref>~~ the ~~ResourceLoader arrived in MediaWiki 1~~.~~17 (2011),~~<ref>{{#cite:~~Q1388~~}}</ref> ~~and '''Parsoid'''~~, the ~~second-generation parser begun in 2012 to enable the visual editor and ported from JavaScript to PHP in 2019, is planned to become the default parser~~ for the ~~entire system —~~ the ~~"unified parser" —~~ in ~~version 1.47, scheduled for November 2026~~.<ref>{{#cite:~~Q1382}}</ref><ref>{{#cite:Q1077}}</ref><ref>{{#cite:Q1387~~}}</ref>		In June 2003, [[Collective:Wikimedia Foundation\|Wikimedia Foundation]] was created under the leadership of [[Person:Jimmy Wales\|Jimmy Wales]]. As a non-profit organisation, it manages Wikipedia's infrastructure and day-to-day operations.<ref>{{#cite:Q1377}}</ref> In July, '''MediaWiki''', a wordplay by [[Person:Daniel Mayer\|Daniel Mayer]] on the Foundation's name.<ref>{{#cite:Q1377}}</ref>, was officially adopted as the name for the software behind Wikipedia. The first release under the new name followed in August 2003.<ref>{{#cite:Q1377}}</ref>

	Today MediaWiki is free software developed in the open by its own community, ~~and — now at stable version 1.46 — it~~ powers tens of thousands of wikis, private and public, including Wikipedia, Wikidata and this very site.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref><ref>{{#cite:Q1378}}</ref>		A new volunteer developer brought in a new killer feature: [[Person:Tim Starling\|Tim Starling]] added '''templates''' to MediaWiki 1.2 (2004), allowing popular elements to be defined once and used on an infinite number of pages. Version 1.3 (August 2004) then expanded them with parameters, moved them into a dedicated <code>Template</code> namespace, and introduced the MonoBook skin as the new default layout.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1379}}</ref>

			Development has continued continuously ever since: the template preprocessor was rewritten in MediaWiki 1.12 (2008);<ref>{{#cite:Q1381}}</ref> the ResourceLoader arrived in MediaWiki 1.17 (2011);<ref>{{#cite:Q1388}}</ref>; the visual editor arrived in 2012; '''Parsoid''', the second-generation parser originally written in Javascript to support the visual editor, was ported to PHP in 2019, with plan to become the default parser for the entire system — the "unified parser" — in version 1.47, scheduled for November 2026.<ref>{{#cite:Q1382}}</ref><ref>{{#cite:Q1077}}</ref><ref>{{#cite:Q1387}}</ref>

			Today, MediaWiki as a free software developed in the open by its own community, powers tens of thousands of wikis, private and public, including Wikipedia, Wikidata and this very site.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref><ref>{{#cite:Q1378}}</ref>

	== Components and interactions ==		== Components and interactions ==

RonzzWikiCowriterAI: Restore "MediaWiki, a wiki engine" heading consumed by the section insert. AI-assisted (RonzzWikiCowriter) (via update-page on MediaWiki MCP Server)

2026-09-01T07:26:19Z

Restore "MediaWiki, a wiki engine" heading consumed by the section insert. AI-assisted (RonzzWikiCowriter) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 07:26, 1 September 2026
Line 2:		Line 2:

	'''MediaWiki''' is the free, open-source wiki engine behind tens of thousands of websites — such as Wikipedia, Wikidata<ref>{{#cite:Q1378}}</ref> — and this very site: RonzzWikiBase.		'''MediaWiki''' is the free, open-source wiki engine behind tens of thousands of websites — such as Wikipedia, Wikidata<ref>{{#cite:Q1378}}</ref> — and this very site: RonzzWikiBase.

			== MediaWiki, a wiki engine ==

	A '''Wiki engine''' powers a '''wiki''': a website hosting static pages, usually informative, which contributors can edit within their browser, with every change tracked and reversible. In its most radical form, e.g., Wikipedia, anyone reading the page can make edits, quickly correcting errors and updating pages.		A '''Wiki engine''' powers a '''wiki''': a website hosting static pages, usually informative, which contributors can edit within their browser, with every change tracked and reversible. In its most radical form, e.g., Wikipedia, anyone reading the page can make edits, quickly correcting errors and updating pages.

RonzzWikiCowriterAI: Add "A short history" section between the intro and Components, imitating HowItWorks:Docker. AI-assisted (RonzzWikiCowriter) (via update-page on MediaWiki MCP Server)

2026-09-01T07:25:24Z

Add "A short history" section between the intro and Components, imitating HowItWorks:Docker. AI-assisted (RonzzWikiCowriter) (via update-page on MediaWiki MCP Server)

@@ Line 2: / Line 2: @@
 '''MediaWiki''' is the free, open-source wiki engine behind tens of thousands of websites — such as Wikipedia, Wikidata<ref>{{#cite:Q1378}}</ref> — and this very site: RonzzWikiBase.
 A '''Wiki engine''' powers a '''wiki''': a website hosting static pages, usually informative, which contributors can edit within their browser, with every change tracked and reversible. In its most radical form, e.g., Wikipedia, anyone reading the page can make edits, quickly correcting errors and updating pages.
@@ Line 10: / Line 8: @@
 MediaWiki, one of the most well-known wiki engines, Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become one of the most well-known wiki engines.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref> Today, it is used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378}}</ref>
 == Components and interactions ==

Rongzhou: /* What is a wiki engine? */

2026-09-01T07:15:10Z

What is a wiki engine?

← Older revision		Revision as of 07:15, 1 September 2026
Line 3:		Line 3:
	'''MediaWiki''' is the free, open-source wiki engine behind tens of thousands of websites — such as Wikipedia, Wikidata<ref>{{#cite:Q1378}}</ref> — and this very site: RonzzWikiBase.		'''MediaWiki''' is the free, open-source wiki engine behind tens of thousands of websites — such as Wikipedia, Wikidata<ref>{{#cite:Q1378}}</ref> — and this very site: RonzzWikiBase.

	== ~~What is~~ a wiki engine? ==		== MediaWiki, a wiki engine ==

	'''Wiki engine''' ~~is the software behind~~ a '''wiki''': a website hosting static pages, usually informative, which contributors can edit within their browser, with every change tracked and reversible~~, hence allowing contributions from a large number of editors located anywhere in the world~~. In its most radical form, e.g., Wikipedia, anyone reading the page can make edits, quickly correcting errors and updating pages.		A '''Wiki engine''' powers a '''wiki''': a website hosting static pages, usually informative, which contributors can edit within their browser, with every change tracked and reversible. In its most radical form, e.g., Wikipedia, anyone reading the page can make edits, quickly correcting errors and updating pages.

	A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.		A wiki engine's most essential job is to store wiki pages in a database, and pull them up for contributors to edit or for the renderer to render pages to HTML for readers on demand. For real-world application, it must also handle authentication, caching, indexing&searching and other auxiliary performance/security needs.

	MediaWiki, one of the most well-known wiki engines, ~~was originally~~ built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia.<ref>{{#cite:Q1377}}</ref> It went through multiple full/partial rewrites ~~— Lee Daniel Crocker rewrote Manske's engine as "Phase III" in 2002 — and~~ the ~~software was renamed "MediaWiki" in 2003, with the first numbered release, 1.1, following in December 2003~~.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref> It is ~~today~~ used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378}}</ref>		MediaWiki, one of the most well-known wiki engines, Originally built as a summer project by early Wikipedia contributor [[Person:Heinrich Magnus Manske\|Magnus Manske]] in 2001 to support a growing Wikipedia,<ref>{{#cite:Q1377}}</ref>, Mediawiki went through multiple full/partial rewrites to become one of the most well-known wiki engines.<ref>{{#cite:Q1377}}</ref><ref>{{#cite:Q1386}}</ref> Today, it is used by tens of thousands of wikis, private and public.<ref>{{#cite:Q1378}}</ref>

	== Components and interactions ==		== Components and interactions ==

Rongzhou: /* The parser stays stable, always stable */

2026-08-31T07:59:36Z

The parser stays stable, always stable

← Older revision		Revision as of 07:59, 31 August 2026
Line 357:		Line 357:

	As such, any proposed changes to the parser must survive extensive scrutiny before being implemented. The wikitext markup MediaWiki uses descends from earlier wiki engines — notably UseModWiki, which ran Wikipedia before MediaWiki and influenced its markup — and grew organically in response to user demand over the years.<ref>{{#cite:Q1377}}</ref> To this day the MediaWiki-flavoured wikitext has not received a formal specification; the closest thing to one is the parser test suite, which mediawiki.org describes as "the authoritative source for Wikitext markup compatibility testing".<ref>{{#cite:Q1390}}</ref> There is however an unofficial spec, jokingly phrased: "whatever the parser spits out, plus a few hundred test cases".		As such, any proposed changes to the parser must survive extensive scrutiny before being implemented. The wikitext markup MediaWiki uses descends from earlier wiki engines — notably UseModWiki, which ran Wikipedia before MediaWiki and influenced its markup — and grew organically in response to user demand over the years.<ref>{{#cite:Q1377}}</ref> To this day the MediaWiki-flavoured wikitext has not received a formal specification; the closest thing to one is the parser test suite, which mediawiki.org describes as "the authoritative source for Wikitext markup compatibility testing".<ref>{{#cite:Q1390}}</ref> There is however an unofficial spec, jokingly phrased: "whatever the parser spits out, plus a few hundred test cases".

			The solution to the problem was to develop a second parser alongside the primary parser. The second parser, as MediaWiki contributors agreed, would not take on any actual functionality until it is proven reliable. The development of the second parser, '''Parsoid''', began in 2012, originally with the aim of supporting MediaWiki's new visual editor. Originally written in JavaScript (Node.js), it was ported to PHP in 2019.<ref>{{#cite:Q1382}}</ref> At the time of writing (2026-08), Parsoid is planned to become the default parser for the entire MediaWiki system — the "unified parser" — in version 1.47, scheduled for November 2026.<ref>{{#cite:Q1077}}</ref><ref>{{#cite:Q1382}}</ref><ref>{{#cite:Q1387}}</ref>

	<uml>		<uml>
Line 431:		Line 433:
	@enduml		@enduml
	</uml>		</uml>


	The solution to the problem was to develop a second parser alongside the primary parser. The second parser, as MediaWiki contributors agreed, would not take on any actual functionality until it is proven reliable. The development of the second parser, '''Parsoid''', began in 2012, originally with the aim of supporting MediaWiki's new visual editor. Originally written in JavaScript (Node.js), it was ported to PHP in 2019.<ref>{{#cite:Q1382}}</ref> At the time of writing (2026-08), Parsoid is planned to become the default parser for the entire MediaWiki system — the "unified parser" — in version 1.47, scheduled for November 2026.<ref>{{#cite:Q1077}}</ref><ref>{{#cite:Q1382}}</ref><ref>{{#cite:Q1387}}</ref>

	=== Templates, lots of templates ===		=== Templates, lots of templates ===

Rongzhou: /* Principal content is created and stored in wikitext */

2026-08-31T07:57:25Z

Principal content is created and stored in wikitext

← Older revision		Revision as of 07:57, 31 August 2026
Line 350:		Line 350:
	</uml>		</uml>

	As can be seen in the above diagram~~. Caching on first read ensures that storing~~ content as wikitext inflicts no performance overhead on read~~. The~~ content is parsed once after every new revision, lazily on read.		As can be seen in the above diagram, Storing content as wikitext inflicts no performance overhead on repeated read as rendered HTML is cached on first read, ensuring that the content is parsed only once after every new revision, lazily on read.

	=== The parser stays stable, always stable ===		=== The parser stays stable, always stable ===