I have a scenario that I don't think fits the usage I've seen for tag-based navigation. Looking for ideas...please weigh in.
I nest 'image-pages' beneath an empty container in the top level of the site tree. I build tag-based lists of these pages on 'galleries' with a multi-select TV that's applied both the image-page and gallery templates. Both instances of the TV have identical input values. I use getResources and &tvfilters to list matches between the two and output the index.
This allows the user to apply any number of tags to image-pages, build galleries to suit, and the site to scale with the user's needs.
But herein lies the challenge, because now I need a nav list on the image-page that's filtered based on the gallery page's tag(s).
This would be a no-brainer in a hierarchical structure, but in my scenario I need to look up to the gallery parent of a child image-page, with the only association between the two a shared tag, and at all children of the container beneath which image-pages are nested, and create an output filtered based on shared tags.
EDIT
The underlying need is to enable an image-page to appear in any gallery at the user's discretion.
The scenario proposed above creates categories before image-pages or galleries are created. If, instead, galleries are treated like categories and created first, then the workflow can changes such that image-pages are assigned galleries (not categories). Same but different?
Is there a way to list galleries (resources) in the image-page editing screen in a selectable fashion, such this selection builds feeds on gallery pages?
[ed. note: wpicotte last edited this post 12 years, 10 months ago.]
