Views: creating a hierarchy of content - am I doing it right?
A taxonomy tree is often the first that comes to mind thinking of a hierarchical directory of content items – but similar structures can also be built in many different ways. Here's just two examples that I personally find often easier to handle, than a taxonomy tree:


Entity reference – rather than having 'lists' of content items 'attached' to taxonomy terms, to me this approach has a more 'real' feel concerning the item-to-item relations. You actually have nodes (items) that can either be partens, children or siblings of nodes (or content types) with all the advatages that come with nodes like commenting etc. And the free tagging reference field let's you even generate new elements 'remotely'.
Book module – probably one of the most underrated core modules – let's you genrate complex tree structures out of the box. While I consider it ideal for a quick start, it might become a bit low-fi in the long run.
 


For me reading this article "RIP Taxonomy Module in Drupal 7" was appeared to be quite helpful when I (again) had to decide how to build a tree of related nodes.