I'm looking for the current best practices of managing complexity of wireframes.
What do you do in the following situations? 1. A page includes multiple panels, each of them is quite complex, with many details and notes. How to show all child panels and their notes without cluttering the parent page's wireframe? 2. A page includes an interactive panel, i.e. one that has multiple states. The size of the interactive panel can be small (i.e. a creeping line) or large (i.e. a tab page). How to show all panel states best? 3. A page includes a panel that is reused on different pages (i.e. as common info block), or multiple times on the same page (e.g. item in a list). How to show the reused panels best, avoiding copying/out-of-sync problems? 4. Different notes and different level of detail should be shown to different audiences. How to create different versions of the same wireframe best? Also what to do if there is not enough room in the sidebar for all footnotes? Thanks! -- View this message in context: http://www.nabble.com/Managing-Complexity-of-Wireframes-tp17532426p17532426.html Sent from the ixda.org - discussion list mailing list archive at Nabble.com. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
