Being fairly new to Episerver, I've encounter requirements where we are listing data on a 'front page' that then lets you click each item and drill down for more information, and as is the nature of lists of items, sometimes it feels appropriate to create different 'views' of the data (e.g. 'show me all products suitable for x. y or z', or 'list only yellow items' etc etc). But up to this point, we've always used 'child pages' for these instances, and then made use of EPiFind or "get children()" methods to then inspect, list or project the data as we need it.
Coming from a more traditional (database heavy) development, if feels like the data we are listing, or drilling down into, should be abstracted away from pages and be handled as data objects themselves.
Bearing in mind the editor experience, and complexity of design (we'd like to keep it simple), have other people encountered this situation, and does anyone have any advice or could recommend some 'best practices' regarding solving this sort of set of requirements?