Messages tagged with #navdsgn

@whitneyhess re #navdsgn great job taking notes. I'd love to see the replies too.

#navdsgn @Pivo1 just cited Bill Buxton and my favorite quote of his about sketching to get the right design vs. getting the design right

#navdsgn "Think of wireframes as disposable sketches." @Pivo1 prefers super low-fidelity wfs. They're exploratory, not skeletons to draw in

#navdsgn Wireframes should reflect the design of schema and systems, not pages. Unnecessary to wireframe every page in a website

#navdsgn ...UIE found no correlation between Bernard's schema and online sales

#navdsgn @jmspool 's study: 44 participants, 13 sites, 1000 transactions. Everyone had enough money to buy what they wanted...

#navdsgn @Pivo1 citing @jmspool 's "Evolution Trumps Usability Guidelines" http://tinyurl.com/5tyday

#navdsgn @Pivo1 citing Michael Bernard's "Developing Schemas for the Location of Common Web Objects" http://is.gd/90ki

#navdsgn Been silent because we're working in teams to design a website for high-end bicycles using the Core & Paths process

#navdsgn ... sketch navigation on core page first > sketch navigation needed on other pages to get to the core. Try it!!

#navdsgn Inward paths: important for findability. Site search, homepage, RSS feeds, open APIs, partner, newsletters, emails, Google

#navdsgn Cores: pages, flow, distributable, multiple cores. Example core: on Flickr -- prioritized element plus supporting info.

#navdsgn @Pivo1 citing Are Halland's Cores & Paths. See his slideshow from IA Summit 2007 here: http://is.gd/8ZTd

#navdsgn Rich Internet Applications (RIAs) - web apps that behave like software apps. Rich in interaction, content, functionality.

#navdsgn I have never been in a workshop that has mentioned @jmspool this much. My reaction (friend!) is so different than a year ago (God!)

#navdsgn @Pivo1 just mentioned Amazon's Mechanical Turk: https://www.mturk.com/mturk/welcome Bidding for jobs. I'd never heard of this!

#navdsgn Extra-site accesses new sites, dramatic transitions/re-orientation, communicates about other services, not prominent but not hidden

#navdsgn Layout: main -- top center, top left or top right; consistent placement throughout site. Local-- top or on sides, closer to content

#navdsgn Design: main -- prominent and large, consistent throughout site; local -- prominent, but not necessarily large or consistent

#navdsgn Interaction: main & local -- v consistent transitions to next pg. Task: main (am I on the right site), local (access specific info)

#navdsgn Categories of nav: structural (links pgs in a hierarchy), associative (links pgs by topic), utility (links to pgs to help use site)

#navdsgn Navigation mechanisms differentiated by: content they access, interaction, task support, visual design, layout and location

#navdsgn URLs should be readable, hackable (to help you understand structure and move from place to place), and "copy-and-paste-able"

#navdsgn Visual Navigation: organic, unstructured diagrammatic representation of content http://visualthesaurus.com/ http://grokker.com

#navdsgn Rotating navigation can be useful with several user types to appeal to w/in limited real estate. However, needs to be right speed

#navdsgn And we're back!

#navdsgn Directory mechanism = all pages of the site listed by "department" -- matches company's organization

#navdsgn Partial site map at bottom of every page becoming popular. More contextual navigation

#navdsgn Bars and Tabs quite commonly used for top navigation. Advantage: see breadth of content in one view. Disadvantage: hard to scale

#navdsgn @Pivo1 citing @keithinstone 's study of breadcrumbs: 1. Location. 2. Path. 3. Attribute. http://instone.org/breadcrumbs/