Difference between revisions of "Wiki Organisation"
From Organic Design wiki
m (Caretaker: Format links, Format cat links, Format headings) |
m (Caretaker: headings) |
||
| Line 2: | Line 2: | ||
Why did we start using Wiki organisation as a precursor to [[Peer-based Organisation]]? | Why did we start using Wiki organisation as a precursor to [[Peer-based Organisation]]? | ||
| − | + | = Collaboration and reuse = | |
*The Wikipedia connection | *The Wikipedia connection | ||
*A large community dedicated to collaborative content creation | *A large community dedicated to collaborative content creation | ||
*A model for [[Organic Design]]? [http://wikimediafoundation.org/wiki/Home Wikimedia] → [http://www.mediawiki.org/wiki/MediaWiki Mediawiki] → [http://en.wikipedia.org/wiki/Main_Page Wikipedia] | *A model for [[Organic Design]]? [http://wikimediafoundation.org/wiki/Home Wikimedia] → [http://www.mediawiki.org/wiki/MediaWiki Mediawiki] → [http://en.wikipedia.org/wiki/Main_Page Wikipedia] | ||
| − | + | = Standout features = | |
*Red Links | *Red Links | ||
*Recent changes | *Recent changes | ||
| Line 14: | Line 14: | ||
*Every page has a web address | *Every page has a web address | ||
| − | + | = What's missing = | |
*Applicational aspects | *Applicational aspects | ||
*The naming problem | *The naming problem | ||
Revision as of 22:03, 12 November 2006
Why did we start using Wiki organisation as a precursor to Peer-based Organisation?
Collaboration and reuse
- The Wikipedia connection
- A large community dedicated to collaborative content creation
- A model for Organic Design? Wikimedia → Mediawiki → Wikipedia
Standout features
- Red Links
- Recent changes
- Discussion
- History
- Every page has a web address
What's missing
- Applicational aspects
- The naming problem
- It is client-server
Despite all of this, Mediawiki, with the improvements added in the form of XmlWiki, proved to be a good enough development environment to begin working on the Peer itself and for us to learn to structure workspaces, in order to prepare content and applicational templates which can easily be ported to the Peer once it is functional. See also: Migration Plan
