Difference between revisions of "Reference:BlueSpiceNamespaceCSS"

(Tag: 2017 source edit)
 

Extension: BlueSpiceNamespaceCSS


Use
Overview
Description: Use different CSS styles for different namespaces. Namespace specific styling
State: stable Dependency: MediaWiki BlueSpice
Developer: HalloWelt License:

GPL-3.0-onlyProperty "BSExtensionInfoLicense" (as page type) with input value "</br>GPL-3.0-only" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Type: MediaWiki BlueSpice Category: Skinning
Edition: BlueSpice free
For more info, visit Mediawiki.

Features[edit source]

, BlueSpice pro, BlueSpice Farm, BlueSpice Cloud

Features

The extension NamespaceCSS allows users to use different CSS styles for different namespaces. This can be

very

useful

to e.g. You can now enter your desired CSS-code directly into this page.

if you want to visually distinguish between different manuals or parts of your wiki.

Technical background[edit | edit source]

Whenever calling up a page in a namespace, the extension NamespaceCss sees if you have defined a "CSS-page" for this namespace in the MediaWiki namespace. If so, this will then be used as stylesheet.

How does NamespaceCss work?[edit | edit source]

For each namespace you want to define your own CSS for, you have to create a page in the MediaWiki namespace, using the following template:

MediaWiki:NamespaceName_css

It is possible to change the look of the wiki at the namespace level.

The CSS code is written to the contents of the <namespace name>_css page. The extension checks at each page call whether there is a CSS page for this namespace. This is then registered as a StyleSheet.

Example: MediaWiki:User_css affects all pages that are in the namespace User.

Please note: The Special namespace is an exception, as you cannot define a separate CSS for it.

Hint[edit | edit source]

Make sure that the following code is part of every MediaWiki:NamespaceName_css page to ensure that the CSS registers properly. Otherwise the VisualEditor might discard your notations:

                 /*
 __NOEDITOR__
 */

            

Technical Information[edit source]

This information applies to BlueSpice 3 . Technical details for BlueSpice cloud can differ in some cases.

Requirements[edit source]

  • MediaWiki: 1.31
  • BlueSpiceFoundation: 3.2

Integrates into[edit source]

Special pages[edit source]

  • BlueSpiceNamespaceCSSManager

Configuration[edit source]

Name Value
NamespaceCSSExcludeNamespaces array ( 0 => -2, )

API Modules[edit source]

  • bs-namespacecss-store

Hooks[edit source]


Attachments

Discussions