The document discusses how the traditional "page" metaphor for web design is becoming outdated as technologies evolve. It explores new interaction design approaches and tools that move beyond page-based thinking, such as rich internet applications, wireflows, and canonical prototyping. While the page still serves as a basic unit currently, the talk suggests the field of information architecture needs to adapt models and practices to account for more fluid, interactive experiences across multiple platforms and devices.

1. R.I.P. Beyond the Page

2. “ The page is dead.” - David Heller

3. Beyond the Page Information Architecture Summit March 7, 2005 Gene Smith “ Turn the Page” - Bob Seger

4. Craftsman vs. Conductor

5. “ Half of my website is in Flash.” - Dennis Schleicher

6. “ We’re in the last days of a static environment.” - Jim Leftwich

7. “ Interaction becomes less browser-centric. Wireframes fall apart.” - Bill DeRouchey

8. “ It’s all about patterns.” - Jim Leftwich

9. The Page

10. This talk is about… The Page Metaphor Its place in IA notation systems And how we think about IA Trends Alternatives

11. "Ideas about organization are always based on implicit images or metaphors that persuade us to see, understand, and manage situations in a particular way.”

12. “ Metaphors create insight. But they also distort. They have strengths. But they also have limitations.” Gareth Morgan Imaginization

13. Technical structure: a network of geographically distributed machines connected via wires organized in a conceptual network of hyperlinks Conceptual structure Moving on a path Toward and into information Paul Maglio & Teenie Matlock “ Metaphors We Surf the Web By” Metaphors we surf by…

14. What is a page anyway? Document Viewed in a web browser Delivered over the Internet via HTTP Linked to other documents Node on a path to some goal Deeply ingrained in IA literature, tools, deliverables

15. “ The basic unit of user experience on the Web is, of course, the page , which we represent as a simple rectangle.” Jesse James Garrett “ A visual vocabulary”

16. “ The [visual] vocabulary currently treats the page as something of a black box” Jesse James Garrett “ The Visual Vocabulary Three Years Later: An Interview with Jesse James Garrett”

17. Page metaphor Page is basic presentation unit Page is basic organizational unit Web is consumed as pages Stuff is assembled into pages

18. Page metaphor Page is basic presentation unit Panels, layers, plug-ins Page is basic organizational unit Granular units (e.g. post) Web is consumed as pages Web is a platform Stuff is assembled into pages “ Stuff” delivered outside the browser

19. IA Notation Systems Flow diagrams (like the Visual Vocabulary) Blueprints & Site Maps Wireframes

20. Disruptive Trends Rich Internet Applications RSS, Atom, XML content Blurred boundaries

21. Rich Internet Applications Internet infrastructure (HTTP) Software interface Flash, Ajax, Java Reduced latency Transparent transitions

28. Impacts Change in focus From IA to Interaction & Interface design From content to software Growth in XML Metrics

29. RSS, Atom, XML content Structured document Built-in validation Multiple nodes Simple, flexible content model

30. c

31. c

33. Impact User chooses how to consume User can choose interface Multiple sources, one interface RSS remix: splicing (union), intersection, frequency, length RSS feeds for everything Need for good content models

34. Blurred boundaries Desktop-web Multiple syncable, sharable Devices Personal-Public IA Web 1.0 – Web 2.0

35. Blurring of Desktop - Web RIAs Macromedia Central Longhorn Mozilla XUL

40. Impacts Abstraction of IA Push to re-use content Design across devices Design across channels

41. Things to think about Page metaphor is web 1.0 Evolving tools Content models Improving metrics

42. Tools to go beyond the page Wireflows Canonical prototyping Content models

43. Wireflows Detail of wireframes Page-level interaction In-page details State, widgets, flow

44. Fulcher, Glass, Leacock Method Simple vocabulary In-page details Supports states and roles Minimal system details

48. Role/State example

49. Some cons of FGL Little abstraction Too detailed? Page based Could be adapted to support RIAs More details (and other tools): http:// leacock.com /deliverables

50. Canonical Prototyping Constantine & Lockwood Toolkit for prototyping Glyphs representing Materials Tools (operations & actions) Active materials (stuff you can do) Micro-patterns

51. Materials

52. Tools

53. Active Materials

54. Example

55. Cons to Canonical Prototyping Too abstract No interplay between containers (aka, “okay, but we still have to deal with pages”) Not plug and play? More details: http:// www.foruse.com/articles/canonical.pdf

56. R.I.P.?

57. “ The page is dead, long live the page.” - David Heller

58. “ The page is a constitutional monarchy” - Marianne Sweeny

59. “ Wherever there’s information… we need to be there architecting that puppy.” - Christina Wodtke

60. Transmedia Transpersonal Transformative Brenda Laurel IA Summit 2004