20090514 Wendling Dan Pecha Kucha Wikis

1,072 views

Published on

For a 6:40 presentation 5/14/2009; Wiki Pecha Kucha for Atlassian Confluence and other wikis.

Published in: Design, Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,072
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

20090514 Wendling Dan Pecha Kucha Wikis

  1. 1. Supporting wiki designers with a Confluence Design Pattern Library Dan Wendling, [email_address] National Library of Medicine Presentation for the Wiki Pecha Kucha, 5/14/2009, http://wiki.sla.org/display/CEWIKI/2009+05+14+~+Sharing+our+Stories+about+Wikis+the+Pecha+Kucha+Way
  2. 2. Core competencies for “The Designer” <ul><li>The Designer: </li></ul><ul><ul><li>Architects new spaces </li></ul></ul><ul><ul><li>Re-architects existing spaces </li></ul></ul><ul><ul><li>Highlights emergent content </li></ul></ul><ul><ul><li>Uses information architecture to improve the user experience </li></ul></ul><ul><ul><li>Shows others how to communicate more effectively </li></ul></ul><ul><ul><li>Conforms to Section 508 (accessibility) rules </li></ul></ul>Wiki Roles The System Administrator The Space Administrator The Designer The Writer The Reader-Commenter The Reader
  3. 3. Design Pattern Library home page <ul><li>6 of 25 entries </li></ul>
  4. 4. DPL home page-list by task
  5. 5. Content chunking; embedding videos
  6. 6. RSS for bringing in content from outside; Tag clouds
  7. 7. Creating a slide show/tutorial; footnotes
  8. 8. Components 1-6 of each design pattern <ul><li>A title that designers identify with </li></ul><ul><li>The design problem </li></ul><ul><li>The solution to this problem </li></ul><ul><li>Illustration with GIF and use case </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul>
  9. 9. Components 7-12 of each design pattern <ul><li>Accessibility issues </li></ul><ul><li>Consequences such as problems that might crop up </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages within the wiki </li></ul><ul><li>Related patterns </li></ul>
  10. 10. Example: The PageTree design pattern <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  11. 11. Illustration for PageTree <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  12. 12. Sample code for PageTree <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  13. 13. When PageTree might be useful <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  14. 14. Accessibility notes for PageTree <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  15. 15. Consequences, Additional resources <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  16. 16. Structural scale, Example pages, Related patterns <ul><li>Title </li></ul><ul><li>Problem summary </li></ul><ul><li>Solution </li></ul><ul><li>Illustration </li></ul><ul><li>Sample code </li></ul><ul><li>When this pattern might be useful </li></ul><ul><li>Accessibility </li></ul><ul><li>Consequences </li></ul><ul><li>Additional resources </li></ul><ul><li>Structural scale </li></ul><ul><li>Example pages </li></ul><ul><li>Related patterns </li></ul>
  17. 17. 9 reasons to implement a design pattern library, 1 st screen <ul><li>(Derived from Lamantia, 2006, 2007) </li></ul><ul><li>Be user-centric; address user experience design challenges; create an effective user experience </li></ul><ul><li>Provide a simple design approach with building blocks </li></ul><ul><li>Provide a structure for growth and evolution </li></ul><ul><li>Increase the value of each individual tool by showing context and the differences between functionalities </li></ul>
  18. 18. 9 reasons to implement, 2 nd <ul><li>Demonstrate new ways to accomplish work, pre-vetted, to increase and improve content assets </li></ul><ul><li>Rapidly create larger units of content from smaller chunks of information </li></ul><ul><li>Ease concerns about problems with enterprise information architecture </li></ul><ul><li>Provide collaboration functionalities that scale up and help you respond to change </li></ul><ul><li>Provide sharing and reuse of familiar, defined blocks of functionality among projects of all sizes and complexity. </li></ul>
  19. 19. What the designer should focus on (e.g., Davenport’s Hierarchy of Information Engagement)
  20. 20. Key influences <ul><li>Barker, Dean T. (2007, July 12). User interface patterns: Reusable solutions for design. White paper. Human Factors International, Inc. Online at: http://humanfactors.com/downloads/whitepapers.asp </li></ul><ul><li>Lamantia, Joe. (2006, 2007). The challenge of dashboards and portals. Part 1 of 6. Boxes and Arrows, August 2007. Online at http://www.boxesandarrows.com/view/the-challenge-of (see all parts) </li></ul><ul><li>Yahoo! Developer Network, Design Pattern Library: http://developer.yahoo.com/ypatterns/index.php </li></ul><ul><li>Tidwell, Jennifer. Designing Interfaces : http://designinginterfaces.com/ </li></ul><ul><li>Davenport, Thomas, and Prusak, Laurence. (1997). Information Ecology: Why technology is not enough for success in the information age. New York: Oxford University Press. p. 93, Hierarchy of information engagement. </li></ul><ul><li>Davenport, Thomas. (2005). Thinking for a living: How to get better performance and results from knowledge workers. Boston: Harvard Business School Press. Chapter 4, Knowledge work processes; chapter 7, Investing in knowledge workers’ networks and learning. </li></ul>
  21. 21. Thanks!

×