• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Information architecture patterns
 

Information architecture patterns

on

  • 7,283 views

Patterns are repeatable solutions to common problems. IA patterns are structures for different kinds of sites. A work in progress, presented at the IA Summit 2010

Patterns are repeatable solutions to common problems. IA patterns are structures for different kinds of sites. A work in progress, presented at the IA Summit 2010

Statistics

Views

Total Views
7,283
Views on SlideShare
6,405
Embed Views
878

Actions

Likes
16
Downloads
143
Comments
0

15 Embeds 878

http://www.boxesandarrows.com 372
http://boxesandarrows.com 296
http://maadmob.com.au 117
http://metablog.borntothink.com 37
http://www.slideshare.net 31
http://xss.yandex.net 8
https://admin.instantpage.me 5
http://feeds.feedburner.com 4
http://jeffhiles.com 2
http://boxesandarrows.mistermachinework.com 1
http://www.newsblur.com 1
http://feedproxy.google.com 1
http://dayangolden.com 1
http://wiki.autodesk.com 1
http://kmnet.renlearn.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Information architecture patterns Information architecture patterns Presentation Transcript

    • Information architecture patterns
    • About me • User experience (IA, IXD, user research, content etc etc)  for 10+ years • Freelance in Canberra, Australia • UX Australia (late August, in Melbourne) • 3 books Card sorting How to write great copy  A practical guide to  for the web information architecture
    • IA patterns A pattern is an emergent  A pattern is an emergent p answer to a common problem
    • Hierarchy
    • Hierarchy • Good for:  Small sites – little need for anything else  When you are guiding, allowing people learn more and  more detail • The relationship between content chunks is naturally  hierarchical  b d broader and narrower d
    • Database
    • Database • Content chunks are independent  There are relationships, but not dependent on each other • Good for:  Single ‘product’ with consistent structure  Storing content once, display it in many ways
    • Hypertext
    • Hypertext • No planned structure • Content is linked together in context • Good for:  Content not known in advance  Developing content domains  Collaborative work • Main challenge ‐ knowing what is available to link to
    • Linear
    • Simple hierarchy & database
    • Simple hierarchy & database • Very common pattern • Good for a wide range of medium sites that have a need  for some database‐style content
    • Catalog
    • Sub-sites
    • Subsites • Good for big organisations with lots of separate  topics/responsibilities • Subsites may have a consistent structure/pattern or vary • Need to decide how often people need to cross between  subsites
    • Focused entry points
    • Why do patterns matter • Help you choose an appropriate way to structure your  content • Provide an overall concept
    • Questions & thanks • http://maadmob.com.au/ htt // d b / • +61 409‐778‐693 • donna@maadmob.net donna@maadmob net • Twitter etc: maadonna