Organic Design Conventions

Organic_Design_Conventions is part of the MediaWiki Workshop. For the latest version of this page, please visit http://www.organicdesign.co.nz/Organic_Design_Conventions

Workflow

Keep main Todo Category uncluttered and containing tasks of general concern, ie not specific user's tasks
Projects are divided up into smaller tasks which are bullet lists to cross off
Sub-lists can form, or they could be linked out to a separate todo-article (esp. if it needs to be done by different role)
Make task names descriptive, but not too long - like an email's subject line or an article's edit summary.
Cross off and append: done by ~~~ at ~~~~~

eg. ~~Get a hair cut~~ done by Nad at 06:57, 12 Oct 2006 (NZST)

Keep content of todo articles to a short description and a bullet list of items
Move todo articles to Category:Done when finished
Use the todo-article's talk page for larger descriptions of details and discussions etc
Use the discussion requests category to indicate tasks waiting for information/decisions etc
Use the Questions:UserName articles to direct questions requiring answers to particular people

Avoid names that could be required by a more general concept.
Forward slashes can be used to divide a name, this format keeps URL's uniform
Whether to make them long descriptive titles, or short ones depends on the contexts of the cats and articles they're used within.
Capital letters - Use capital first letter always except for filenames and specifics like iPod, only use other capitals for proper nouns.
The default move operation is now rename which frees up the original title without making a redirect. Make a redirect if the original title linked to a lot or still in common use.

Start top level headings with "=="
Only use the # style when its absolutely necessary to have outline-numbering that work with embedding

Use the MediaWiki transclusion syntax unless you need to apply-code or embed script or something else using the XmlWiki properties
To use MediaWiki transclusion without templates, use a preceeding : before the article name

Article size
Edit summary
Minor edit
Editing user-talk pages
- Add new comments below the existing item they are with respect to and indent one more level than that item, this way the conversation thread is clear (also such threads will migrated into the peer environment as threads).
- Add new threads/topic to the top, not bottom (I didn't get round to changing the "+" edit to do that, so don't use it), and use a ---- separator to signify the thread change.
- Use --~~~~ signiture at the end of your comment, or on next line indented to same level.
Fix up items to conform to the conventions when you come across them

Login to edit: We use this policy on our wiki's not because we want to reduce accessibility in any way or to force people to register, but rather because all our regular users would frequently forget to sign in and would appear as IP addresses in the recent changes instead of as their username.