EWTE/booknav/pm: Difference between revisions
From OER in Education
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* Adding a page to a set of pages requires the book definition to be updated. | * Adding a page to a set of pages requires the book definition to be updated. | ||
* While it's easy to edit the book (and thereby the navigation), and this may already be familiar to users, every time the book is saved the <nowiki><noinclude></nowiki> statements need to be added again to the book definition, for the navigation to stay properly formatted. | * While it's easy to edit the book (and thereby the navigation), and this may already be familiar to users, every time the book is saved the <nowiki><noinclude></nowiki> statements need to be added again to the book definition, for the navigation to stay properly formatted. | ||
* | * The page itself does not 'know' that it's part of the book, and can 'behave' accordingly, e.g. it's not possible to add "previous" and "next" navigation to pages. | ||
Latest revision as of 16:14, 5 January 2015
Advantages are:
- This method is quite simple to use, and builds on using the book creator. Users can use the interface provided by the book creator to create their collections.
- It also means that books cannot just be viewed (as a set of wiki pages), but also exported, using the mechanisms provided by the book creator. The pages are thus grouped on the wiki, and can be exported as such.
However, there are a number of disadvantages:
- Adding a page to a set of pages requires the book definition to be updated.
- While it's easy to edit the book (and thereby the navigation), and this may already be familiar to users, every time the book is saved the <noinclude> statements need to be added again to the book definition, for the navigation to stay properly formatted.
- The page itself does not 'know' that it's part of the book, and can 'behave' accordingly, e.g. it's not possible to add "previous" and "next" navigation to pages.
