This is essentially two separate requests, but one can't effectively stand alone without the other.
In the example below I'm hacking together a solution to create a subnav based on tags, which reloads the page and filters the content respective to the selection. In this instance, since we are allowing our members to submit properties (another hack using the 'idea' post), this isn't an ideal solution since the nav menu on the left isn't dynamically generated. Even the 'tags' callout on the right will require moderation since there's no way to narrow the visible tags to a group (i.e. 'countries') and I don't want it to show every single tag.
I see a couple solutions to this:
Provide more view options for the 'tags' block (list, gallery, carousel, etc.) which would allow more customization to simulate a nav menu
Provide the ability to sync the 'list menu' block with tags/tag groups or Db fields
Either way, the ability to create tag groups (i.e. 'Countries') that would have nested tags (i.e. Costa Rica, Peru, etc.) will be essential to create dynamic menus so that the admin can specify the group to pull from, versus tags (which might not exist yet).
A less ideal solution would be tag pairing, or essentially using conditional logic to identify the tags that should be dynamically generated in a selected menu (i.e. if tag is [country] add [other_tag] to [list menu]).
