Wiki Advice: Difference between revisions
Jump to navigation
Jump to search
(Created page with "==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 Manage...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| 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 adapt as you go. | |||
adapt as you go. | #Eliminate all duplication that naturally occurs. | ||
#Build just enough structure. When a page hits 100 lines break it into multiple subtopics. | |||
#Always be adjusting and optimizing the overall site navigation and structure. | |||
multiple subtopics. | #Provide a 10,000-foot view of the whole thing. | ||
#Practice active wiki gardening | |||
structure. | #Don't put "coming soon" stuff up. Wait till it comes. | ||
==See Also== | ==See Also== | ||
Latest 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:
- Create something that people can use on day 1. Gather feedback and adapt as you go.
- Eliminate all duplication that naturally occurs.
- Build just enough structure. When a page hits 100 lines break it into multiple subtopics.
- Always be adjusting and optimizing the overall site navigation and structure.
- Provide a 10,000-foot view of the whole thing.
- Practice active wiki gardening
- Don't put "coming soon" stuff up. Wait till it comes.