THAT sounds *much* cooler (and more useful) than having another vocabulary for modules to try slotting themselves into. <br><br>+++1 for implementing that instead. <br><br><div class="gmail_quote">On Fri, Feb 13, 2009 at 12:15 AM, Nathaniel Catchpole <span dir="ltr"><<a href="mailto:catch56@googlemail.com">catch56@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In the redesign discussions, we'd discussed having nodereferences between case studies, site recipes and projects for this purpose rather than tags. That way, people documenting how particular types of sites are built could show which modules they used - as opposed to project owners saying 'I think this might be useful for'. You could then show showcases and site recipes next to modules, and modules next to showcases and site recipes in a structured way (and with some data munging, get aggregate data if needed). Was this discussed as an option?<br>
<br>Nat<br><br>
</blockquote></div><br>