Manual:$wgExtraNamespaces/en

<translate> Namespaces</translate>: $wgExtraNamespaces
Additional namespaces.
<translate> Introduced in version:</translate>	1.3.3
<translate> Removed in version:</translate>	<translate> still in use</translate>
<translate> Allowed values:</translate>	(array)
<translate> Default value:</translate>	[]
<translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate>

Details

The $wgExtraNamespaces configuration parameter lets you configure additional, custom namespaces . It can also be used to rename the default namespaces. See the manual on using custom namespaces for further details.

Developer information:

In case an extension should work with the newly created custom namespace, make sure that you define and name them prior to invoking the respective extension.

Extensions should not use this configuration parameter. Instead they should use the CanonicalNamespaces hook or load the namespace through extension.json (MW 1.26+, Gerrit change 234146).

See also

• Namespace IDs used by extensions – Shows you a list of namespace IDs you should definitely avoid to prevent namespace conflicts, thus the first custom namespace may encounter conflicts even at ID 110 though 100 is theoretically possible. It is recommened to define custom namespaces with IDs starting at 3000 to avoid namespace conflicts.
• $wgExtraGenderNamespaces
• $wgNamespaceAliases