mediawiki-skins-Vector/includes/templates/LegacySidebar.mustache

{{!
	See @typedef SidebarData
}}
<div id="mw-panel" class="vector-legacy-sidebar">
	<div id="p-logo" role="banner">
		<a class="mw-wiki-logo" href="{{link-mainpage}}"
			title="{{msg-tooltip-p-logo}}"></a>
	</div>
	{{#data-portlets-first}}{{>LegacyMenu}}{{/data-portlets-first}}
	{{#array-portlets-rest}}{{>LegacyMenu}}{{/array-portlets-rest}}
	{{#data-portlets.data-languages}}{{>LegacyMenu}}{{/data-portlets.data-languages}}
</div>
Technical: Use unambigious menu template Follow up to 49c8b5f51496d9863a0040ab4df7292db6b0d922 Our PHP parser resolves >Menu to the parent directory which differs from the frontend Mustache library. Best to have different names for these files to avoid this problem. Bug: T311319 Change-Id: Iea708718a0b928c4902dc7bac0c5ee304b89f961 2022-06-25 00:18:17 +00:00			`{{!`
			`See @typedef SidebarData`
			`}}`
Legacy: Group template/styles together to avoid confusion This was confusing me while working on the Portal.mustache file. Bug: T317899 Change-Id: I884cd33938b2670bddc90f698d8f61f37c6c29d4 2022-11-30 20:52:03 +00:00			`<div id="mw-panel" class="vector-legacy-sidebar">`
Technical: Use unambigious menu template Follow up to 49c8b5f51496d9863a0040ab4df7292db6b0d922 Our PHP parser resolves >Menu to the parent directory which differs from the frontend Mustache library. Best to have different names for these files to avoid this problem. Bug: T311319 Change-Id: Iea708718a0b928c4902dc7bac0c5ee304b89f961 2022-06-25 00:18:17 +00:00			`<div id="p-logo" role="banner">`
			`<a class="mw-wiki-logo" href="{{link-mainpage}}"`
			`title="{{msg-tooltip-p-logo}}"></a>`
			`</div>`
			`{{#data-portlets-first}}{{>LegacyMenu}}{{/data-portlets-first}}`
			`{{#array-portlets-rest}}{{>LegacyMenu}}{{/array-portlets-rest}}`
			`{{#data-portlets.data-languages}}{{>LegacyMenu}}{{/data-portlets.data-languages}}`
			`</div>`