EWTE/nav/plusminus - Revision history

Bjoern at 16:14, 5 January 2015

2015-01-05T16:14:44Z

← Older revision		Revision as of 16:14, 5 January 2015
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.
	* Allows for 'previous' and 'next' links.		* 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.

Bjoern at 16:13, 5 January 2015

2015-01-05T16:13:44Z

← Older revision		Revision as of 16:13, 5 January 2015
Line 2:		Line 2:
	* 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.
	* Allows for 'previous' and 'next' links.		* Allows 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.

Bjoern at 16:04, 5 January 2015

2015-01-05T16:04:54Z

← Older revision		Revision as of 16:04, 5 January 2015
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 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.
	* Allows for 'previous' and 'next' links.		* Allows for 'previous' and 'next' links.
	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.

Bjoern at 12:22, 5 January 2015

2015-01-05T12:22:39Z

← Older revision		Revision as of 12:22, 5 January 2015
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:~~BasePageNav~~]] to a set of pages (and sub-pages) to create navigation.		* Flexible creation of navigation, as simple as adding a generic template [[Template:BasePageGroupNav]] to a set of pages (and sub-pages) to create navigation.
	* Allows for 'previous' and 'next' links.		* Allows for 'previous' and 'next' links.
	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.

Bjoern: Created page with "The advantages of this approach are: * Flexible creation of navigation, as simple as adding a generic template Template:BasePageNav to a set of pages (and sub-pages) to cr..."

2015-01-05T12:21:20Z

Created page with "The advantages of this approach are: * Flexible creation of navigation, as simple as adding a generic template Template:BasePageNav to a set of pages (and sub-pages) to cr..."

New page

The advantages of this approach are:
* Flexible creation of navigation, as simple as adding a generic template [[Template:BasePageNav]] to a set of pages (and sub-pages) to create navigation.
* Allows 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.