Weakinesses

In light of Wiki troubles the Pie/Echo/Atom group is having, I thought I should just jot down some suggestions that could reduce some of the problems.

Stop Flash Floods

A busy Wiki page accumulates a lot of information quickly and the urge to reorganize the page in mass mounts.  Don't.  People identify a page by its content, not just its title.  Editing the page, particularly the first two screens of content are like flash floods that wash away recognizable landmarks and leave the Wiki user disoriented.

Instead, create another page and point to it.  This means introduction of page versions where each version represents structural changes.  Within each version, changes are accumulative.  There must also be a way to link to most recent version and list and enumerate the versions.  Page versions account for ahistoric nature of Wiki to some extent.

Doors, Places, and Objects

While every Wiki page are web pages, you must assign distinctive roles to those pages.  Some pages act as doors, directing or discouraging movement to places and objects.  Some pages act as places serving as containers for objects like documents and provide constraints for activities such as general musings or topic related discussions.

Pages acting as objects like documents should have a clear division between the object and the actions.  For example, Wiki page for Archiving API spec should have the draft spec at the top and discussion about the API at the bottom.

Too Many Pages

Discourage creation of Wiki pages on whims.  Assign people rights or buffer with a wait period (1 day) before a new page can be created.  Similar pages should be merged by adding a new page instead of deleting or reorganizing.