I’ve written a new module called PageTree, that allows you to create arbitrary page navigation structures, with any level of heirarchy.
Each “page” object has metadata (title, short description), and linking info (template group/name and optional entry id, or a static url). Pages have any number of child pages, with any level of nesting.
You can then use tags in your templates to render those trees in different ways (eg: breadcrumbs, section nav, sitemap). The tags can auto-detect the current page, based on the query string (ie: it looks for a page that matches the current template/entry combination), or you can supply it at a parameter.
It has a few funky features, like auto-exporting the page structure into a specified category group, allowing you to associate weblog entries to pages (in addition to associating pages to weblog entries). This is nice for doing things like sidebar elements that you want to post to multiple “pages”.
I’m pretty sure people might find this module useful.
I’d like to make it available to the community, but I’m concerned about the codebase. While I’ve coded it all myself, I’ve used chunks of the built-in Weblog module’s code as “inspiration”.
I need some advice on whether this module is distributable. I’m happy to supply the MOD and MCP files to someone from pMachine, to see what you think, and I’m happy to “clean room” any contentious chunks of code.
If this is OK’d, please don’t forget to add it to our list of modules. =)