3 ms·
This. The term "wiki" really just means quickly/easily editable (hyper)text. It's a shame it's sort of grown to mean "text that will magically maintain itself".
by e12e 13y ago
This. The term "wiki" really just means quickly/easily editable (hyper)text. It's a shame it's sort of grown to mean "text that will magically maintain itself". Just like "just open source it" isn't a solution to library maintenance (but can be a prerequisite for community contribution) - "put up a wiki" doesn't mean the thing will curate itself.
I'm reminded of a quote by Cunningham where he says that his most frequent actions on wikis are to delete and consolidate content.
Maintaining a wiki takes work. Having an editor, along with a process for going over material regularly (say once a month) helps a lot. That and/or have "owners" for pages and sections (eg: the developer responsible for the gizmorenderer gets reminders to review the example code and documentation for the renderer, while the devops lead gets reminders to review the install/setup instructions etc). If a section hasn't been marked "good" for the past two-three months - have the system delete it.
Encourage people to review old documentation/pages when writing new -- maybe update a few old examples and add new ones, rather than just add a single new example that covers the new API etc.
Tooling and automatic reminders can help, but at the core what is needed is a (business) process for maintaining the thing -- it can be completely manual -- but it needs to be there.