Wiki Patterns

Patterns for successful wiki use

User Tools

Site Tools


lunch_menu

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

lunch_menu [2018/11/14 22:14]
127.0.0.1 external edit
lunch_menu [2018/11/28 15:01] (current)
splitbrain
Line 1: Line 1:
-===== Lunch Menu ===== +====== Lunch Menu ======
- +
-==== What is it? ====+
  
 The Lunch Menu pattern encourages you to put time-sensitive content on the wiki. If there is content you know will be updated regularly, like a weekly ​ [[http://​www.flickr.com/​photos/​brettlider/​sets/​154249/​|cafeteria]] ​ menu, put it on the wiki rather than sending it out on the email distribution list. The Lunch Menu pattern encourages you to put time-sensitive content on the wiki. If there is content you know will be updated regularly, like a weekly ​ [[http://​www.flickr.com/​photos/​brettlider/​sets/​154249/​|cafeteria]] ​ menu, put it on the wiki rather than sending it out on the email distribution list.
Line 7: Line 5:
 By centralizing the dynamic content and never emailing it, the team always knows where to look, and never runs the risk of finding out-dated information. By centralizing the dynamic content and never emailing it, the team always knows where to look, and never runs the risk of finding out-dated information.
  
-==== Usage ====+===== Usage =====
  
 Identify content that changes frequently and build wiki pages around it. You can make useful, always current pages about many topics: Identify content that changes frequently and build wiki pages around it. You can make useful, always current pages about many topics:
Line 15: Line 13:
   * Software build and test results   * Software build and test results
  
-==== Example ====+===== Example ​=====
  
-The classic business-development "deal list" is a great candidate for the [[Lunch+Menu|Lunch Menu]] pattern. In the pre-wiki-world,​ business development folks usually kept a spreadsheet detailing the current status of all their leads. They'd email that sheet out to their team-members to keep them up to date on the status. By putting that time-sensitive content on the wiki, the team can go straight to where they //know// the most up-to-date content will be.+The classic business-development "deal list" is a great candidate for the [[Lunch Menu]] pattern. In the pre-wiki-world,​ business development folks usually kept a spreadsheet detailing the current status of all their leads. They'd email that sheet out to their team-members to keep them up to date on the status. By putting that time-sensitive content on the wiki, the team can go straight to where they //know// the most up-to-date content will be.
  
-==== Related Patterns ====+===== Related Patterns ​=====
  
-  * [[Magnet|Magnet]] - the magnet pattern emphasizes putting content exclusively on the wiki to attract people. Regularly updated, time-sensitive content is a perfect candidate for this. +  * [[Magnet]] - the magnet pattern emphasizes putting content exclusively on the wiki to attract people. Regularly updated, time-sensitive content is a perfect candidate for this. 
-  * [[Poker|Poker]] - this pattern encourages putting informal content on the wiki to give people further reason to visit and contribute to it.+  * [[Poker]] - this pattern encourages putting informal content on the wiki to give people further reason to visit and contribute to it.
  
-==== Further Reading ====+===== Further Reading ​=====
  
   *  [[http://​c2.com/​w4/​apl4tec/​wiki.cgi?​TimeSensitiveAndLocationSensitive|Wiki:​ Time Sensitive and Location Sensitive]] ​   *  [[http://​c2.com/​w4/​apl4tec/​wiki.cgi?​TimeSensitiveAndLocationSensitive|Wiki:​ Time Sensitive and Location Sensitive]] ​
Line 31: Line 29:
  
 ---- struct data ---- ---- struct data ----
 +classification.type ​ : Pattern
 +classification.focus : Adoption
 ---- ----
  
lunch_menu.txt · Last modified: 2018/11/28 15:01 by splitbrain