Wiki Advice: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
code. Obey the following rules to maximize your success:
code. Obey the following rules to maximize your success:


*Create something that people can use on day 1. Gather feedback and
#Create something that people can use on day 1. Gather feedback and
adapt as you go.
adapt as you go.
*Eliminate all duplication that naturally occurs.
#Eliminate all duplication that naturally occurs.
*Build just enough structure. When a page hits 100 lines break it into
#Build just enough structure. When a page hits 100 lines break it into multiple subtopics.
multiple subtopics.
#Always be adjusting and optimizing the overall site navigation and structure.
*Always be adjusting and optimizing the overall site navigation and
#Provide a 10,000-foot view of the whole thing.
structure.
#Practice active wiki gardening
*Provide a 10,000-foot view of the whole thing.
#Don't put "coming soon" stuff up. Wait till it comes.
*Practice active wiki gardening
*Don't put "coming soon" stuff up. Wait till it comes.


==See Also==
==See Also==

Revision as of 15:41, 21 September 2011

Overview

Below is some advice on wiki management by Mark Seaman (a "wiki-expert").

Notes

Mark Seaman - I've worked on a large number of these type of "Knowledge Management" projects in the past. I take an approach that is very similar to writing code. Obey the following rules to maximize your success:

  1. Create something that people can use on day 1. Gather feedback and

adapt as you go.

  1. Eliminate all duplication that naturally occurs.
  2. Build just enough structure. When a page hits 100 lines break it into multiple subtopics.
  3. Always be adjusting and optimizing the overall site navigation and structure.
  4. Provide a 10,000-foot view of the whole thing.
  5. Practice active wiki gardening
  6. Don't put "coming soon" stuff up. Wait till it comes.

See Also

Wiki map