Manual:Extension/TabberNeue: Difference between revisions

No edit summary
Tag: 2017 source edit
No edit summary
Line 72: Line 72:


=== Example ===
=== Example ===
Show the content of the pages Mytransclusion1 and Mytransclusion2 in tabs.<syntaxhighlight lang="text">
Show the content of the pages ''Mytransclusion''1 and ''Mytransclusion2'' in tabs.<syntaxhighlight lang="text">
<tabbertransclude>
<tabbertransclude>
Mytransclusion1|Page 1
Mytransclusion1|Page 1

Revision as of 08:56, 16 April 2024

TabberNeue is available from BlueSpice 4.4.

Simple Tabs

If you want to organize page content in tabs, you can use a special syntax in source editing mode.

The contents of the tabs cannot be edited in visual editing mode. It is, however, possible to show (transclude) entire wiki pages as the content of the tabs.


Tabs are created with tabName=tabBody and separated by |-|. You can use any content in the tabs, including templates and images.

4 tabs with the content of the first tab shown.
Simple tabs
If you insert the tabs via the Visual Editor Insert menu, omit the beginning and ending <tabber> and </tabber> tags.
<tabber>
|-|Titel für Tab 1=
Content for Tab 1.
|-|Titel für Tab 2=
Content for Tab 2.
|-|Title for Tab 3=
Content for Tab 3.
</tabber>

Nested Tabs

Nested tabbers must be written as parser functions. Instead of the <tabber/> tags, they are enclosed with {{#tag:tabber|}} and separated by {{!}}-{{!}}.

Example of 4 tabs. The sub-tabs of the 1st main tab are open.
Nested tabs
If you insert the tabs via the Visual Editor Insert menu, omit the beginning and ending <tabber> and </tabber> tags.


<tabber>
|-|First Tab Title=
{{#tag:tabber|
 Tab Title A=
 Tab content A goes here.
 {{!}}-{{!}}
 Tab Title B=
 Tab content B goes here.
 {{!}}-{{!}}
 Tab Title C=
 Tab content C goes here.
 }}
|-|Second Tab Title=
{{#tag:tabber|
 Tab Title D=
 Tab content D goes here.
 {{!}}-{{!}}
 Tab Title E=
 Tab content E goes here.
 {{!}}-{{!}}
 Tab Title F=
 Tab content F goes here.
 }}
|-|Third Tab Title=
{{#tag:tabber|
 Tab Title G=
 Tab content G goes here.
 {{!}}-{{!}}
 Tab Title H=
 Tab content H goes here.
 {{!}}-{{!}}
 Tab Title I=
 Tab content I goes here.
 }}
</tabber>

Transclusion

With the transclusion mode, the entire contents of the page of the first tab will be transcluded. The transcluded pages in other tabs will be transcluded on-demand with AJAX, performing a request to the MediaWiki api. Once requested, they won't be fetched again until the page is reloaded. Note that Tabbers on the transcluded page will not be rendered. Tabs are created with pageName|tabName, and separated by a new line.

If you insert the tabs via the Visual Editor Insert menu, omit the beginning and ending <tabbertransclude> and </tabbertransclude> tags.


<tabbertransclude>
First Page Name|First Tab Title
Second Page Name|Second Tab Title
Third Page Name|Third Tab Title
</tabbertransclude>

Example

Show the content of the pages Mytransclusion1 and Mytransclusion2 in tabs.

<tabbertransclude>
Mytransclusion1|Page 1
Mytransclusion2|Page 2
</tabbertransclude>

To create the tabs:

  1. Select Insert>Tabber(transclusion) in the editor toolbar.
  2. Write the necessary lines in the tabber inspector pop-up:
  3. Click Done.
  4. Save the page.
    Mytransclusion1|Page 1
    Mytransclusion2|Page 2
    
inspector window with code for transcluding two pages in two tabs.
Inspector window for transcluding two pages


This is the output:

This content comes from the page Mytransclusion1.

Maintenance categories

This extension automatically inserts a tracking category on pages with tabs. To suppress them, change the content of the related system messages.

  1. Go to page Special:TrackingCategories in your wiki.
  2. Click on tabberneue-tabber-category and tabberneue-tabbertransclude-category in the column Message name (2nd column).
  3. Replace the existing content with a dash ("-"). The category will no longer be displayed on your wiki pages.
  4. Save the page.

The system category is no longer displayed on your wiki pages.

See also: [1]



To submit feedback about this documentation, visit our community forum.