What's the best way to....

... group a bunch of pages together so it's easy to navigate between them?

Should I put them all in a book, or use categories, or a header or sideblock or somesuch?

(Here's an example of such a collection).

I mean, my ideal situation - which may not be possible - is to have a menu on the left or right to navigate to any of those pages. Those aren't the whole wiki, of course, they're just a corner of it.

With some coding, you can create your own permanent sideblocks by creating classes in vault/core/model/block and vault/core/view/factory/block and by adding an appropriate entry to the database in the vw_block table.

If you aren't feeling that adventurous, you can create a sidebar block using BB-Code.

Code:

---

[div] position="sidebar" |
BB-Code content
[/div]

---

You would have to put this BB-Code on every page where you want your nav-block, so you should probably create a wiki template and include that on your pages. It will make it easier to manage.

It sounds like the sidebar block BB Code version is the way to go. I'll give it a try! Though if that's going to appear on the page itself (rather than in an actual sidebar) won't that clash messily with the automatic page table of contents?

It will appear in the sidebar. If you use position="sidebar" as above.

Oh, I see! That's clever! :)

OK, I don't quite understand how to do this.

I created a template in the Templates area called "13thagemenu":

http://www.enworld.org/forum/showwik...es:13thagemenu

I then inserted the text "[template]13thagemenu[/template] on a page:

http://www.enworld.org/forum/showwik...haracter-Rules

And it showed the "[div] position="sidebar" |" code without parsing it and didn't put it in a sidebar.

Go to VaultWiki Admin Panel > Content > Syntax Manager, and make sure that the DIV BB-Code is enabled in wiki pages. Also, double-check your template area and make sure that BB-Code is allowed.

Div wasn't enabled; fixed that which stopped the raw code showing.

It still isn't in the sidebar though!

Thanks for the report. Here's the bug: https://www.vaultwiki.org/issues/3477/

It's now working for you.

Perfect! Thanks!