EWTE/nav/plusminus: Difference between revisions
From OER in Education
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The advantages of this approach are: | The advantages of this approach are: | ||
* Flexible creation of navigation, as simple as adding a generic template ([[Template:BasePageGroupNav]]) to each in a set of pages (and sub-pages) to create navigation. | * Flexible creation of navigation, as simple as adding a generic template ([[Template:BasePageGroupNav]]) to each in a set of pages (and sub-pages) to create navigation. | ||
* The page itself 'knows' that it's part of the book (and where it is in the book), and can 'behave' accordingly, e.g. allowing for 'previous' and 'next' links. | |||
* The page itself 'knows' that it's part of the book, and can 'behave' accordingly. | |||
The disadvantages of this approach are: | The disadvantages of this approach are: | ||
* It does require a number of extensions to be installed (semantic mediawiki, as well as functions for arrays). | * It does require a number of extensions to be installed (semantic mediawiki, as well as functions for arrays). | ||
* It does not integrate with the book extension, when in principle the functionality is similar. | * It does not integrate with the book extension, when in principle the functionality is similar. | ||
Latest revision as of 16:14, 5 January 2015
The advantages of this approach are:
- Flexible creation of navigation, as simple as adding a generic template (Template:BasePageGroupNav) to each in a set of pages (and sub-pages) to create navigation.
- The page itself 'knows' that it's part of the book (and where it is in the book), and can 'behave' accordingly, e.g. allowing for 'previous' and 'next' links.
The disadvantages of this approach are:
- It does require a number of extensions to be installed (semantic mediawiki, as well as functions for arrays).
- It does not integrate with the book extension, when in principle the functionality is similar.
