Originally the SoSLUG site relied on views and a free tagging taxonomy to navigate the site. Consequently few items of content appeared in any menu structure, rather content was related by a taxonomy term, and listed by the date it was posted?. For news items, forums, and events, this approach has an obvious advantage, since this content is ordered by time.
From the outset, web design took a different approach, favouring a menu system to structure the content. In common with the HowTo's etc. on the SoSLUG site, its content is primarily instructional. In this instance, content is ordered by subject, having little or no time dependence. Top level menu items provide a broad introduction, which can then be broken down into progressively more detail at each sub level in the menu.
A problem with any menu structure arises when content can be placed in different menu locations. To overcome this, taxonomy terms are used to cross reference different sections.
A menu structure has now been added to SoSLUG, and the taxonomy tidied up. but the dilemma hasn't go away, the site needs both menu and views, if news, and events are not to be buried in a menu somewhere. How do we resolve this?
A view can be a page or a block. The latter can be embedded in a page (node), which overcomes the maintenance issue of page views not counting as nodes.