Does someone have ideas on how make the wiki grow faster?
http://wiki.softwarecraftsmanship.org
--
twitter.com/olofb
olofb.wordpress.com
olofb.wordpress.com/tag/english
I've been keeping a wiki for my own use (to keep my head on in an allegedly
straight fashion) for several years now, and I've been using Dokuwiki for
this and several client projects for 3-4 years now.
Namespaces in DW are a great organizational aid *if* they're used with some
forethought. It helps to be ruthlessly Linnaean in your taxonomy. There is
little penalty for building deep hierarchies rather than just a "bag of
reasonably related bits" (which is what most casual Wikis eventually turn
into).
As always, and unsurprisingly for us, some best practices seem apparent.
When DW is given a namespace as a link (with or without a terminating
colon), it follows the rules specified here
(http://www.dokuwiki.org/namespaces#namespace_default_linking) to resolve
that namespace into a link which references a page. So what fairly obviously
falls out of this is what I and a few other users I've seen do, which can be
illustrated here, with * indicating a namespace and - a page:
* ...
* ops_and_maintenance_notes
* imac
* installed_apps
- komodo_edit
- ...
- start (for 'installed_apps')
- start (for 'imac')
- start (for 'ops_and_maintenance_notes')
* ...
Each namespace always has a 'start' page, which will be the default page for
that namespace per the rules linked to above. That 'start' page should have
descriptive text that essentially justifies the namespace in terms of the
organizational needs and usage of the wiki. It should have links in it to
each page in the namespace, especially if the wiki isn't using one of the
several good 'menu' plugins for DW (which I see the SC wiki isn't :( ).
One significant benefit of this organization is that, as the wiki expands,
topics which start as pages can be replaced by namespaces, with *none* of
the linking Wiki pages needing to change; instead of linking directly to the
target page, their link will resolve to the 'start' page of the new
namespace.
And yes, all this should be in the SC Wiki somewhere - both to help new
users understand How Things Work and to serve as a living policy statement.
One of the things DW has historically fallen down on when it's used by a
large, diverse user base is that there isn't a MediaWiki-style "discussion"
page linked to each article page in the default configuration. Like many
(most?) DW "deficiencies", that can be rectified through the use of a
plugin, available from http://www.dokuwiki.org/plugin:discussion.
I don't think it's practical anymore to have a "community" online without
some sort of Wiki; mailing-list archives are useful, but they lack the
discoverability and semantics of a good Wiki. Good Wikis, therefore, tend to
have (and require) both a vibrant community and a knowledgeable, benevolent
editor (curator/dictator) to come along and help clean things up as needed.
Just my two rupiah worth...
Jeff
--
Jeff Dickey http://archlever.blogspot.com
Email: jdi...@seven-sigma.com
Phone/SMS: +65 8333 4403
Skype: jeff_dickey
LinkedIn: jdickey
Yahoo! IM: jeff_dickey
MSN IM: jeff_...@hotmail.com (for IM only, not for email, please)
ICQ: 8053918
QQ: 30302349
GnuPG key:
Fingerprint D367 FB97 4E59 BEC0 8EBC D8E3 3BD4 7D4C DFE0 6488
Valid 01/07/2009 to 31/12/2009
Download from http://tr.im/qqQa
Mailing lists don't tend to condense the knowledge of the community in
a form friendly to introduce to new members. (Why spend so much time
on one mail?) By the same token, mailing lists are great at exploring
different points of view. (A few clicks, press send, and now I've
publicly disagreed with you.) Fortunately, many a community (or field
of study, or train of thought) has at least one person interested in
reconciling its confused history, if only for their own benefit.
> Jeff
Jason Catena