Your SlideShare is downloading. ×

URL Design for Information Architects

8,754

Published on

1 Comment
36 Likes
Statistics
Notes
  • great presentation
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
8,754
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
202
Comments
1
Likes
36
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. URL Design for Information Architects Deanna Marbeck Silver Oliver
    • 2. What we are going to tell you
      • Why you should care about URLs
      • How to design beautiful URLs
      • When to think about URL design
      • What deliverables come out of the design process
    • 3. What we are not going to tell you
      • What are URLs
    • 4. Do you design URLs?
    • 5. Why do I care about URL design?
      • First 10 minutes of my working day
    • 6.  
    • 7.  
    • 8.  
    • 9.  
    • 10.  
    • 11.  
    • 12.
      • www.hotmail.com
    • 13.  
    • 14.  
    • 15.
      • http://icanhascheezburger.com/2008/08/27/funny-pictures-how-many-calorees/
    • 16.  
    • 17.
      • http:// mikeschinkel.com/blog/welldesignedurlsarebeautiful /
    • 18.  
    • 19.  
    • 20.
      • http://www.currybet.net/cbet_blog/2008/04/doctor_wh
    • 21.  
    • 22.
      • http://www.currybet.net/cbet_blog/2008/04/doctor_wh
    • 23.
      • http://www.currybet.net/cbet_blog/2008/04/
    • 24.  
    • 25.
      • doctor_who_rss_url.php 17-Jun-2008 07:42
    • 26.  
    • 27.  
    • 28.  
    • 29.
      • http://www.bbc.co.uk/doctorwho/news/cult/news/drwho/2008/04/22/54453.shtml
    • 30.  
    • 31.  
    • 32.  
    • 33.
      • http://www.bbc.co.uk/doctorwho/news/cult/news/drwho/2008/04/22/54453.shtml
    • 34.  
    • 35.  
    • 36. What does this all mean?
    • 37. URLs are as important as the logos and navigation of a site http://www.bbc.co.uk/doctorwho/
    • 38.  
    • 39. What helps you design these URLs?
    • 40. The guiding principles
      • Persistent
      • Readable
      • Hackable
    • 41. Which takes priority?
    • 42. Maslow’s hierarchy of needs
    • 43. Maslow’s hierarchy of needs Persistent
    • 44. Persistent
      • Why?
      • Other sites link to you
      • Users bookmark you
      • Search engines find you
    • 45.  
    • 46.  
    • 47.  
    • 48.
      • http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e
    • 49. Persistent
      • Prince?
      • The Artist Formerly Known As Prince?
      • Symbol?
      • The Purple One?
      • Prince Rogers Nelson?
    • 50. Persistent
      • Prince?
      • The Artist Formerly Known As Prince?
      • The Purple One?
      • Prince Rogers Nelson?
      http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e
    • 51. “ Designing mostly means leaving information out” Sir Tim Berners-Lee said that
    • 52. What NOT to put in URLs
      • Author’s name
      • Status
      • Subject
      • Filename extensions
      • Software mechanisms
      • Session ids
    • 53.
      • http://open.bbc.co.uk/labs/innovation_labs_future_media_t.php
    • 54. Maslow’s hierarchy of needs Persistent
    • 55. Human Readable
      • Why?
      • Don’t only appear in the address bar
      • Easy to understand
      • Easy to remember
      • More meaningful
      • Arguably some SEO benefit
    • 56.  
    • 57.
      • www.bbc.co.uk/topics/dogs
    • 58.  
    • 59. Human Readable
      • rubbishandrecycling?
      • rubbish-and-recycling?
      • rubbish_and_recycling?
      • special characters
    • 60.
      • ~
    • 61. Human Readable
      • rubbishandrecycling?
      • rubbish-and-recycling?
      • rubbish_and_recycling?
      • special characters
      • length
    • 62. Maslow’s hierarchy of needs Persistent
    • 63. Hackable
      • Why?
      • Represents the logical structure of your site
      • Provides extra information – orientation within the site
      • Lets people move to higher levels of your site
      • Lets people guess the address for a similar resource
    • 64.  
    • 65.  
    • 66. http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/04
    • 67. Hackable
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/04
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/10
    • 68. http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/10
    • 69. Hackable
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/04
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/10
      • http://www.bbc.co.uk/bbcfour/programmes
    • 70. http://www.bbc.co.uk/bbcfour/programmes
    • 71. Hackable
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/04
      • http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/08/10
      • http:// www.bbc.co.uk/bbcfour/programmes
      • http://www.bbc.co.uk/bbcfour
    • 72. http://www.bbc.co.uk/bbcfour
    • 73. Hackable
      • Consistent use of labels
      • Similar resources should sit at the same level
      • Provide a meaningful page for every level of your hierarchy
    • 74. The guiding principles
      • Persistent
      • Readable
      • Hackable
    • 75. It’s a balancing act
    • 76. Maslow’s hierarchy of needs Persistent
    • 77. The design process and deliverables
    • 78. Why do I care?
    • 79. Michael Smethurst
    • 80. aka My Boss
    • 81. Traditional IA
    • 82.  
    • 83. bbc.co.uk/programmes
    • 84. Elegant, extensible, logical
    • 85. “ What URL is that at?”
    • 86. http://flickr.com/photos/hurleygurley/4338767/
    • 87. When?
    • 88. At the beginning of the design process
      • Understand user requirements
      • Understand business requirements
      • Understand your data – domain model
    • 89. http://www.bbc.co.uk/music/beta
    • 90. Music Domain Model
    • 91. Design your URLs
      • Make your schema
      • Understand the relationships between your data
      • Design your URLs from the bottom up
      • One URL for every resource
    • 92. Music Domain Model
    • 93. http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e/releases/singles
    • 94. http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e/releases
    • 95. http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e
    • 96. http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e
    • 97. http://www.bbc.co.uk/music/artists
    • 98. http://www.bbc.co.uk/music/artists/070d193a-845c-479f-980e-bef15710653e.xml
    • 99. Music URLs
      • /music/artists/:artist/releases/:releasetype
      • /music/artists/:artist/releases
      • /music/artists/:artist
      • /music/artists
      • /music
      • /music/about
      • /music/developers
      • /music/contactus
    • 100. More music URLs
      • /music/labels
      • /music/labels/:label
      • /music/labels/:label/releases
      • /music/labels/:label/releases/:type
      • /music/labels/:label/artists
      • /music/releases
      • /music/releases/:release
      • /music/releases/:release/tracks
      • /music/releases/:release/events
      • /music/releases/:release/contributors
      • /music/releases/:release/links
    • 101. Now you have a site structure
    • 102. Job done! http://flickr.com/photos/neloqua/243001463/
    • 103. Deliverables
    • 104. Communication
      • Walls of URLs
      • Lists of pages
      • Wireframes
      • Designs
      • Prototypes
    • 105. URLs on postits
    • 106. Walls of URLs
    • 107. URL syntax
      • :artist
      • {service}
      • /music/artists/:artist
      • /{service}/programmes
    • 108. Involve your team
    • 109. Spreadsheets
    • 110. http://www.flickr.com/photos/suneko/373318607/
    • 111. Sitemaps
    • 112. Schematic
    • 113. Designs
    • 114. Prototype - http://www.bbc.co.uk/music/artists
    • 115. http://www.flickr.com/photos/purrr/126597849/
    • 116. Job done! http://flickr.com/photos/neloqua/243001463/
    • 117. Summary
      • URLs are part of the user experience
      • Information Architects should be involved in the design of URLs
      • Create beautiful URLs and beautiful site structures
    • 118. thank/you [email_address] [email_address]

    ×