Revision history for StyleGuide


Revision [16477]

Last edited on 2016-02-21 19:33:18 by DominiqueKoppes
Deletions:
=== Quick Tips for Informative Wiki Writing===
[[http://www.explorewriting.co.uk/InformativeWriting.html Source]]
1. What's the Point?
2. Ditch the Flowery Prose
3. Put Your Feelings Aside
4. Get Your Facts Straight
5. Go to the Sources


Revision [16476]

Edited on 2016-02-21 19:31:54 by DominiqueKoppes
Additions:
[[http://www.explorewriting.co.uk/InformativeWriting.html Source]]
1. What's the Point?
2. Ditch the Flowery Prose
3. Put Your Feelings Aside
4. Get Your Facts Straight
5. Go to the Sources
Deletions:
1. What's the Point?
2. Ditch the Flowery Prose
3. Put Your Feelings Aside
4. Get Your Facts Straight
5. Go to the Sources


Revision [16475]

Edited on 2016-02-21 19:30:27 by DominiqueKoppes
Additions:
=== Quick Tips for Informative Wiki Writing===
1. What's the Point?
2. Ditch the Flowery Prose
3. Put Your Feelings Aside
4. Get Your Facts Straight
5. Go to the Sources


Revision [13486]

Edited on 2014-02-18 13:21:05 by MorganAdmin
Additions:
~- ClichedThought (yet another iteration of WhatEverybodyAlreadyKnows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say.
Deletions:
~- ClichedThought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say.


Revision [13485]

Edited on 2014-02-18 13:20:16 by MorganAdmin

No Differences

Revision [13461]

Edited on 2014-02-17 08:02:40 by MorganAdmin
Additions:
=== Nix to NeutralPOV ===
Deletions:
=== NeutralPOV ===


Revision [13337]

Edited on 2014-02-10 07:33:24 by MorganAdmin
Additions:
Have a look at the UC Davis style guide: http://daviswiki.org/Wiki_Style_Guide Not to emulate but as a comparison.


Revision [13225]

Edited on 2013-08-23 08:39:24 by MorganAdmin
Additions:
- For DocumentMode, we use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others //can// elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you. This page is an example of DocumentMode.
- For ThreadMode, we use first person. You may sign your entries, or remain anonymous.
- On this wiki, we place the DocumentMode section at the top of the page, followed by ThreadMode contributions. We use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
- Add notes, comments, first-person anecdotes, questions, personal opinions in ThreadMode where they seem to fit best on the page. Sign them, or not. Expect someone to review ThreadMode contributions occasionally, to refactor them, reorganize them, and roll them into DocumentMode. That someone is you.
- The conventions of citation and quotation apply on a wiki. When you borrow or quote, cite; and if the source is online, link to it. Use only those images you have permission to use, and give credit.
- Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens. We are.
Deletions:
~- For DocumentMode, we use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others //can// elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you. This page is an example of DocumentMode.
~- For ThreadMode, we use first person. You may sign your entries, or remain anonymous.
~- On this wiki, we place the DocumentMode section at the top of the page, followed by ThreadMode contributions. We use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
~- Add notes, comments, first-person anecdotes, questions, personal opinions in ThreadMode where they seem to fit best on the page. Sign them, or not. Expect someone to review ThreadMode contributions occasionally, to refactor them, reorganize them, and roll them into DocumentMode. That someone is you.
~- The conventions of citation and quotation apply on a wiki. When you borrow or quote, cite; and if the source is online, link to it. Use only those images you have permission to use, and give credit.
~- Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens. We are.


Revision [12926]

Edited on 2013-03-06 07:06:48 by MorganAdmin
Additions:
=== NeutralPOV ===
We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use //we//, not //I//, and not the invisible I of the passive, nor the invisible mass of "some people." We get in close enough to name names.
Deletions:
NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive, nor the invisible mass of "some people." We name names and groups.


Revision [12925]

Edited on 2013-03-06 07:05:37 by MorganAdmin
Additions:
NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive, nor the invisible mass of "some people." We name names and groups.
Deletions:
NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive.


Revision [12924]

Edited on 2013-03-06 07:03:25 by MorganAdmin
Additions:
NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive.
Deletions:
~- NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive.


Revision [12922]

Edited on 2013-03-06 07:01:26 by MorganAdmin
Additions:
~- NeutralPOV. We're not about NPOV. Balance, consideration, decorum, openness, and BalconyView. But Wikipedia does NPOV, so we don't need to. We use we, not I, and not the invisible I of the passive.


Revision [12603]

Edited on 2013-02-27 05:58:14 by MorganAdmin
Additions:
~- ClichedThought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say.
Deletions:
~- ClichédThought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say.


Revision [12601]

Edited on 2013-02-27 05:55:48 by MorganAdmin
Additions:
~- For DocumentMode, we use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others //can// elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you. This page is an example of DocumentMode.
~- For ThreadMode, we use first person. You may sign your entries, or remain anonymous.
Deletions:
~- For DocumentMode, use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others //can// elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you.
~- For ThreadMode, use first person. You may sign your entries, or remain anonymous.


Revision [12559]

Edited on 2013-02-23 15:44:43 by MorganAdmin
Additions:
>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a TextInProgress.>>====Weblogs and Wikis Style Guide====
Deletions:
>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>====Weblogs and Wikis Style Guide====


Revision [12558]

Edited on 2013-02-23 15:43:32 by MorganAdmin
Additions:
~- For DocumentMode, use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others //can// elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you.
~- On this wiki, we place the DocumentMode section at the top of the page, followed by ThreadMode contributions. We use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
~- Add notes, comments, first-person anecdotes, questions, personal opinions in ThreadMode where they seem to fit best on the page. Sign them, or not. Expect someone to review ThreadMode contributions occasionally, to refactor them, reorganize them, and roll them into DocumentMode. That someone is you.
~- Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens. We are.
Newcomers to a wiki are often apprehensive about contributing. [more] The material above the DoubleLine is DocumentMode and is owned by the wiki: it represents the collective effort of all contributors and is expected to change. The material below the DoubleLine is considered discussion and dissent. Our aim is not to quiet dissent but to incorporate it into DocumentMode. Wikis don't work by consent but by dissent, discussion, synthesis.
~- Review the threads until you see a pattern or structure to the comments and discussion. Summarize or synthesize that pattern and roll it into the DocumentMode.
''Let's add a WelcomeRitual. And practice good [[http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices]]Review and draft our own DialoguePractices.'' See WikiWallflowers
~ There are people for whom, in the strictest of self-interest, WikiWiki is a learning place. For some it is a knowledge base. For others it is a forum for debate. All find something of value. Ward Cunningham and Bo Leuf, TheWikiWay, p ?
We encourage a variety of rhetorical manners on this wiki, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. In another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
When you encounter a page, take a moment to consider the rhetorical manner that seems at work. What's going on here? Is this a formal debate? A sermon? A casual exchange of views? A dialogue? Adjust your rhetorical approach and manner accordingly. Or refactor the page towards a new rhetorical manner.
>>We've found that rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, AgonisticWriting so much as a space for DeliberativeWriting, its development would favor rhetorical strategies of invention and deliberation over sermons, standup routines, and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.>>=== Some general guidelines ===
~- ClichédThought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say.
~- On a wiki, ideas rule. Posing and posturing offer little to development. When the prose is more about the writer than the subject, the writer gets in the way of the ideas.
>>SunirShah writes, Here's a little game I play:
When a topic worth pursuing arises in a face to face conversation, we make a mental note to move the conversation back to the topic later. We do the same on this wiki by leaving and placing WikiWords in ThreadMode entries, taking care to maintain the writer's meaning.
~- Page Summaries We like to use page summaries on this wiki to help others quickly get oriented to the page. Post a page summary at the top of the page, laying out what the page will cover or do. Change the summary as the page evolves. We also use this summary area to list what needs to be done on the page.
We figure readers can and will read intellegently and will spend some energy reading - if the pay-off is worth it. Wikis are places of thought and consideration, not hit and run. Short and sweet have a place, but really gain their meaning in context of considered and nuanced.
Paragraphs are meaningful units of discourse. They can be long and developed, short and pithy, and in between. Paragraph.
Deletions:
~- For DocumentMode, use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others can elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you.
~- Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But ~as a thread gets long, move it below the DoubleLines.
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting (at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.
~- Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens.
Newcomers to a wiki are often apprehensive about contributing. [more] The material above the DoubleLine is DocumentMode and is owned by the wiki: it represents the collective effort of all contributors and is expected to change. The material below the DoubleLine is considered discussion and dissent. Our aim is not to quiet dissent but to incorporate it into DocumentMode.
~- Review the threads until you see a pattern or structure. Add the structural outline to the page to help others refactor.
''to do and add: Consider writing a WelcomeRitual. And practice good [[http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices]]Review and draft our own DialoguePractices.'' See WikiWallflowers
~ There are people for whom, in the strictest of self-interest, WikiWiki is a learning place. For some it is a knowledge base. For others it is a forum for debate. All find something of value. Ward Cunningham and Bo Leuf
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. In another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
When you encounter a page, take a moment to consider the rhetorical manner that seems at work. What's going on here? Is this a formal debate? A sermon? A casual exchange of views? A dialogue? Adjust your rhetorical approach and manner accordingly.
>>Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.>>=== Some general guidelines ===
~- Clichéd thought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say. And on a related note,
~- On a wiki, ideas rule. Posing and posturing offer little to development. When the prose is more about the writer than the subject, the writer gets in the way of the ideas.
>>Here's a little game I play:
If a topic worth pursuing arises in a conversation, we make a mental note to return to it later. On the BlogsAndWikis wiki, it's good practice to create a WikiWord in someone's ThreadMode entry, taking care to maintain the writer's meaning.
~- Page Summaries We like to use page summaries on this wiki to help others quickly get oriented to the page. Post a page summary at the top of the page, laying out what the page will cover or do. Change the summary as the page evolves. Writers can also use this summary area to list what needs to be done on the page.
We figure readers can and will read intellegently and will spend some energy reading - if the pay-off is worth it. Wikis are places of thought and consideration, not hit and run. Short and sweet might have a place, but it can be empty and superficial, terse and canned.
Paragraphs are meaningful units of discourse. They can be long and developed, short and pithy, and in between. Please paragraph.


Revision [11150]

Edited on 2012-02-15 10:25:38 by KevinMcColley
Additions:
~- Concision is noble. Concision keeps the signal to noise ratio up (high signal, low noise), and it allows others to contribute.
Deletions:
~- Concision is nobel. Concision keeps the signal to noise ratio up (high signal, low noise), and it allows others to contribute.


Revision [11143]

Edited on 2012-02-15 10:15:53 by OrieHouse [Typo fixin]
Additions:
Newcomers to a wiki are often apprehensive about contributing. [more] The material above the DoubleLine is DocumentMode and is owned by the wiki: it represents the collective effort of all contributors and is expected to change. The material below the DoubleLine is considered discussion and dissent. Our aim is not to quiet dissent but to incorporate it into DocumentMode.
Deletions:
Newcomers to a wiki are often apprehensive about contributing. [more] The material above the DoubleLine is DocumentMode and is owned by the wiiki: it represents the collective effort of all contributers and is expected to change. The material below the DoubleLine is considered discussion and dissent. Our aim is not to quiet dissent but to incorporate it into DocumentMode.


Revision [11136]

Edited on 2012-02-15 06:29:59 by MorganAdmin [Typo fixin]
Additions:


Revision [10788]

Edited on 2012-02-08 06:33:01 by MorganAdmin [Typo fixin]
Additions:
- [[http://biro.erhetoric.org/wikka.php?wakka=NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]], on Morgan's wiki at biro.erhetoric.org.
Deletions:
- [[http://biro.erhetoric.org/wikka.php?wakka=NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]], on Morgan's wiki at biro.erhetoric.


Revision [10787]

Edited on 2012-02-08 06:32:49 by MorganAdmin [Typo fixin]
Additions:
- [[http://biro.erhetoric.org/wikka.php?wakka=NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]], on Morgan's wiki at biro.erhetoric.
Deletions:
- [[http://biro.erhetoric.org/wikka.php?wakka=NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]]


Revision [10786]

Edited on 2012-02-08 06:32:12 by MorganAdmin [Typo fixin]
Additions:
- [[http://biro.erhetoric.org/wikka.php?wakka=NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]]
Deletions:
- [[http://biro.erhetoric.org/NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]]


Revision [10488]

Edited on 2011-06-09 07:22:26 by MorganAdmin [Typo fixin]
Additions:
- [[http://biro.erhetoric.org/NotesTowardsARhetoricOfWikis Notes Towards a Rhetoric of Wiki]]
Deletions:
- [[http://biro.bemidjistate.edu/cgi/notebook.pl?NotesTowardsARhetoricOfWiki/ComposingProcesses Notes Towards a Rhetoric of Wiki]]


Revision [9728]

Edited on 2011-02-02 21:27:12 by DestinyHarmoning [Typo fixin]
Additions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. In another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
Deletions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.


Revision [9162]

Edited on 2010-07-09 08:43:01 by MorganAdmin [Typo fixin]
Additions:
''to do and add: Consider writing a WelcomeRitual. And practice good [[http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices]]Review and draft our own DialoguePractices.'' See WikiWallflowers
Deletions:
''to do and add: Consider writing a WelcomeRitual. And practice good [[http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices]]Review and draft our own DialoguePractices.''


Revision [8389]

Edited on 2010-02-08 18:14:58 by PhilPeterson [Typo fixin]
Additions:
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting (at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.
Deletions:
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting ( at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.


Revision [8388]

Edited on 2010-02-08 18:14:38 by PhilPeterson [Typo fixin]
Additions:
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting ( at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.
Deletions:
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting (: at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.


Revision [8318]

Edited on 2010-02-06 19:08:36 by TammiHartung [Typo fixin]
Additions:
Use complex sentences to articulate complex ideas. We don't want to limit the range of expression by banning complex-compound sentences or limiting punctuation. So we aren't adverse to complex but clear sentences, employing semi-colons, colons, dashes, even ellipses where appropriate to make meaning.
Deletions:
Use complex sentences to articulate complex ideas. We don't to limit the range of expression by banning complex-compound sentences or limiting punctuation. So we aren't adverse to complex but clear sentences, employing semi-colons, colons, dashes, even ellipses where appropriate to make meaning.


Revision [5877]

Edited on 2009-01-16 17:28:07 by RyanWells [Removing unnecessary space]
Additions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
Deletions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated
debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.


Revision [3528]

Edited on 2008-02-15 14:32:05 by MorganAdmin [Removing unnecessary space]
Additions:
- CollaborateRadically


Revision [3525]

Edited on 2008-02-15 14:27:50 by MorganAdmin [Removing unnecessary space]
Additions:
sources: Draft borrowed from [[http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]]. But in good WikiFashion, the original draft is now more obscured than visible. I've taken [[http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 Wiki Good Style]] as a model for this refactoring. MorganMC
Deletions:
sources: Draft borrowed from [http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]. But in good WikiFashion, the original draft is now more obscured than visible. I've taken [[http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 Wiki Good Style]] as a model for this refactoring. MorganMC


Revision [3524]

Edited on 2008-02-15 14:26:56 by MorganAdmin [Removing unnecessary space]
Additions:
A mighty fine [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide StyleGuide at Meatball]]
Deletions:
A mighty fine StyleGuide over at [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball]]


Revision [3523]

Edited on 2008-02-15 14:26:34 by MorganAdmin [Removing unnecessary space]
Additions:
A mighty fine StyleGuide over at [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball]]


Revision [3222]

Edited on 2008-02-13 07:40:20 by MorganAdmin [Removing unnecessary space]
Additions:
''to do and add: Consider writing a WelcomeRitual. And practice good [[http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices]]Review and draft our own DialoguePractices.''
sources: Draft borrowed from [http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]. But in good WikiFashion, the original draft is now more obscured than visible. I've taken [[http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 Wiki Good Style]] as a model for this refactoring. MorganMC
Deletions:
'' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''
sources: ''Draft borrowed from [http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]. But in good WikiFashion, the original draft is now more obscured than visible.'' I've taken http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 as a model for this refactoring. MorganMN


Revision [2934]

Edited on 2007-12-26 13:36:27 by MorganAdmin [Removing unnecessary space]
Additions:
CategoryWiki CategoryWikiHandbook
Deletions:
CategoryWiki CategoryWritingWithAWiki


Revision [2872]

Edited on 2007-12-26 12:21:27 by MorganAdmin [Removing unnecessary space]
Additions:
CategoryWiki CategoryWritingWithAWiki
Deletions:
CategoryWiki


Revision [830]

Edited on 2007-02-11 10:11:22 by MorganMC [Removing unnecessary space]
Additions:
sources: ''Draft borrowed from [http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]. But in good WikiFashion, the original draft is now more obscured than visible.'' I've taken http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 as a model for this refactoring. MorganMN
See also
- [[http://biro.bemidjistate.edu/cgi/notebook.pl?NotesTowardsARhetoricOfWiki/ComposingProcesses Notes Towards a Rhetoric of Wiki]]
- CollaborationConventions
Deletions:
I've taken http://www.seedwiki.com/page.cfm?doc=Wiki%20Good%20Style&wikiid=1231&wpid=77845 as a model for this refactoring. [[M C Morgan]]
~- http://biro.bemidjistate.edu/cgi/notebook.pl?NotesTowardsARhetoricOfWiki/ComposingProcesses
CollaborationConventions
sources: ''Draft borrowed from [http://www.weblogKitchen.com/wiki.cgi?StyleGuide the style guide at weblogKitchen.com]. But in good WikiFashion, the original draft is now more obscured than visible.''


Revision [434]

Edited on 2007-01-10 13:40:08 by MorganMC [Removing unnecessary space]
Additions:
CategoryWiki


Revision [416]

Edited on 2007-01-08 23:19:53 by MorganAdmin [Removing unnecessary space]
Additions:
>>Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]>>=== Getting Started ===
Deletions:
=== Getting Started ===>>Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]>>


Revision [415]

Edited on 2007-01-08 23:18:55 by MorganAdmin [Removing unnecessary space]
Additions:
=== Getting Started ===>>Here's a little game I play:
Deletions:
=== Getting Started ===
>>Here's a little game I play:


Revision [414]

Edited on 2007-01-08 23:18:19 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [413]

Edited on 2007-01-08 23:17:41 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [412]

Edited on 2007-01-08 23:16:57 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [411]

Edited on 2007-01-08 23:15:57 by MorganAdmin [Removing unnecessary space]
Additions:
>>Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.>>=== Some general guidelines ===
Deletions:
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<=== Some general guidelines ===


Revision [410]

Edited on 2007-01-08 23:15:17 by MorganAdmin [Removing unnecessary space]
Additions:
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<=== Some general guidelines ===
Deletions:
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<
=== Some general guidelines ===


Revision [404]

Edited on 2007-01-08 23:11:08 by MorganAdmin [Removing unnecessary space]
Additions:
>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>====Weblogs and Wikis Style Guide====
Deletions:
====Weblogs and Wikis Style Guide====>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>


Revision [403]

Edited on 2007-01-08 23:10:27 by MorganAdmin [Removing unnecessary space]
Additions:
====Weblogs and Wikis Style Guide====>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>
Deletions:
====Weblogs and Wikis Style Guide====
>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>


Revision [402]

Edited on 2007-01-08 23:10:02 by MorganAdmin [Removing unnecessary space]
Additions:
>>Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.>>
Deletions:
Writing on a wiki proceeds from ThreadMode to DocumentMode by way of RefactoringPages. These modes are not HardAndFastRules but ways of approaching a text-in-progress.


Revision [384]

Edited on 2007-01-08 22:44:40 by MorganAdmin [Removing unnecessary space]
Additions:
>>Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]>>
Deletions:
>>----
Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]
---->>


Revision [377]

Edited on 2007-01-08 22:12:05 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [376]

Edited on 2007-01-08 22:08:56 by MorganAdmin [Removing unnecessary space]
Additions:
debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<
Deletions:
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.


Revision [375]

Edited on 2007-01-08 22:08:02 by MorganAdmin [Removing unnecessary space]
Additions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
Deletions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<


Revision [374]

Edited on 2007-01-08 22:07:00 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [373]

Edited on 2007-01-08 22:04:58 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [372]

Edited on 2007-01-08 22:03:47 by MorganAdmin [Removing unnecessary space]
Additions:
<<Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.<<
Deletions:
Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.


Revision [371]

Edited on 2007-01-08 22:01:40 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [370]

Edited on 2007-01-08 22:00:35 by MorganAdmin [Removing unnecessary space]
Additions:
====Weblogs and Wikis Style Guide====
Deletions:
====Wiki Style Guide====


Revision [369]

Edited on 2007-01-08 22:00:09 by MorganAdmin [Removing unnecessary space]
Additions:
=== Jumping In: Contributing ===
Deletions:
=== jumping in: contributing ===


Revision [368]

Edited on 2007-01-08 21:59:13 by MorganAdmin [Removing unnecessary space]
Deletions:
::c::


Revision [367]

Edited on 2007-01-08 21:58:39 by MorganAdmin [Removing unnecessary space]
Additions:
::c::


Revision [366]

Edited on 2007-01-08 21:57:51 by MorganAdmin [Removing unnecessary space]
Additions:
>>----
Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]
---->>
Deletions:
>>Here's a little game I play:
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]>>


Revision [365]

Edited on 2007-01-08 21:56:41 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [364]

Edited on 2007-01-08 21:55:34 by MorganAdmin [Removing unnecessary space]

No Differences

Revision [363]

Edited on 2007-01-08 21:54:19 by MorganAdmin [Removing unnecessary space]
Additions:
>>Here's a little game I play:
Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.
When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.
You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]>>
Deletions:
~ Here's a little game I play:
~ Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.
~ When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.
~ You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]


Revision [362]

Edited on 2007-01-08 21:51:36 by MorganAdmin [Removing unnecessary space]
Additions:
Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures. But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode. If you get on a soapbox, expect a response. Expect to be refactored into moderation.
Deletions:
~ Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures.
~ But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode.
~ If you get on a soapbox, expect a response. Expect to be factored out.


Revision [361]

Edited on 2007-01-08 21:48:57 by MorganAdmin [Removing unnecessary space]
Additions:
We encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.
Deletions:
This wiki would like to encourage a variety of rhetorical manners, from lectures to casual discussion. Think of moving from room to room at a party. In each room, there's an exchange going on. In one room, one person holds the floor with a thoughtful, balanced lecture. in another, a small group is having a heated debate. In another, a group of strangers are exchanging the first tentative remarks about an issue of the day.


Revision [360]

Edited on 2007-01-08 21:47:03 by MorganAdmin [Removing unnecessary space]
Additions:
'' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''
Deletions:
- '' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''


Revision [359]

Edited on 2007-01-08 21:46:30 by MorganAdmin [Removing unnecessary space]
Additions:
~- Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But ~as a thread gets long, move it below the DoubleLines.
- '' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''
Deletions:
~- Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
'' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''


Revision [358]

Edited on 2007-01-08 21:45:05 by MorganAdmin [Removing unnecessary space]
Additions:
'' to do and add: Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]''
Deletions:
Consider WelcomeRitual. And practice good [http://c2.com/cgi/wiki?DialoguePractices Dialogue Practices] [links to c2.com. Review, and draft our own DialoguePractices.]


Revision [120]

Edited on 2006-12-13 13:09:22 by MorganMC [Removing unnecessary space]

No Differences

Revision [119]

Edited on 2006-12-13 13:08:42 by MorganMC [Removing unnecessary space]
Additions:
====Wiki Style Guide====
Deletions:
=====Wiki Style Guide=====


Revision [118]

Edited on 2006-12-13 13:08:16 by MorganMC [Removing unnecessary space]
Additions:
~ Here's a little game I play:
~ Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.
~ When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.
~ You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]
Deletions:
~ ''Here's a little game I play:''
~ ''Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.''
~ ''When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.''
~ ''You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]''


Revision [117]

Edited on 2006-12-13 13:07:22 by MorganMC [Removing unnecessary space]
Additions:
=====Wiki Style Guide=====
~- For DocumentMode, use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others can elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you.
~- For ThreadMode, use first person. You may sign your entries, or remain anonymous.
~- Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
~- Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting (: at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.
~- The conventions of citation and quotation apply on a wiki. When you borrow or quote, cite; and if the source is online, link to it. Use only those images you have permission to use, and give credit.
~- Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens.
~- Leave the signed entry. Refactor the ideas into the DocumentMode above the line, but leave the original signed material.
~- Review the threads until you see a pattern or structure. Add the structural outline to the page to help others refactor.
~- ...
~ There are people for whom, in the strictest of self-interest, WikiWiki is a learning place. For some it is a knowledge base. For others it is a forum for debate. All find something of value. Ward Cunningham and Bo Leuf
~ Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures.
~ But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode.
~ If you get on a soapbox, expect a response. Expect to be factored out.
~ ''Here's a little game I play:''
~ ''Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.''
~ ''When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.''
~ ''You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [[http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]]''
~- Civility and understatement give contributors space to work. Namecalling and writing to annoy others spoils the pool. Write to make this a comfortable place to work.
~- There doesn't seem to be much profit in writing off the cuff on a wiki - even in ThreadMode. WikiStyle is a thoughtful, crafted style.
~- Concision is nobel. Concision keeps the signal to noise ratio up (high signal, low noise), and it allows others to contribute.
~- Clichéd thought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say. And on a related note,
~- On a wiki, ideas rule. Posing and posturing offer little to development. When the prose is more about the writer than the subject, the writer gets in the way of the ideas.
~- Structure the page
~- Reorganize the page
~- Trim ThreadMode comments to bring the gist forward so others can respond to it.
~- Refactor the page to DocumentMode
~- Heads and subheads help create structure which helps create meaning. Structure pages using TextFormattingRules.
~- Bulleted lists can be AGoodThing. But don't let lists stand in for DiscursiveProse. Use lists as an element of DiscursiveProse.
~- Page Summaries We like to use page summaries on this wiki to help others quickly get oriented to the page. Post a page summary at the top of the page, laying out what the page will cover or do. Change the summary as the page evolves. Writers can also use this summary area to list what needs to be done on the page.
~- Summarizing the main points of a page can provide a fresh start for refactoring.
~- Links: Use descriptive link text and consider where the links might be placed on the page: in line or called out.
~- Refactoring might entail finding a PagePattern to help organize the content. Heads and subheads signal the PagePattern.
~- Refactor pages to emphasize the structure of ideas, not the chronology of contribution.
~- Roll ThreadMode material and ideas into DocumentMode. Recast the prose in a clear, concise, third-person voice, maintaining the ideas but giving them structure.
~- A page can be broken up into several pages if the threads seem to become to convoluted and need clarification.
~- If you see an infelicity, a typo, a misspelling, fix it silently.
~- Edit sentences and paragraphs for concision and clarity.
~- http://biro.bemidjistate.edu/cgi/notebook.pl?NotesTowardsARhetoricOfWiki/ComposingProcesses
Deletions:
* For DocumentMode, use a clear but informal, third-person, active voice. Expect others to elaborate or complete your writing. Write so that others can elaborate. If you wish, you can sign your WikiName at the bottom of the DocumentMode section as a contributer. Or not. Up to you.
* For ThreadMode, use first person. You may sign your entries, or remain anonymous.
* Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines.
* Add notes, comments, first-person anecdotes, personal opinions in ThreadMode where they seem to fit best on the page. Set them apart by indenting (: at the beginning of the line), or by setting them in italics. Someone will begin to roll your ThreadMode contributions into the document.
* The conventions of citation and quotation apply on a wiki. When you borrow or quote, cite; and if the source is online, link to it. Use only those images you have permission to use, and give credit.
* Expect to have your words folded into refactorings as the page develops towards DocumentMode. Be flattered when it happens.
* Leave the signed entry. Refactor the ideas into the DocumentMode above the line, but leave the original signed material.
* Review the threads until you see a pattern or structure. Add the structural outline to the page to help others refactor.
*
: ''There are people for whom, in the strictest of self-interest, WikiWiki is a learning place. For some it is a knowledge base. For others it is a forum for debate. All find something of value.'' Ward Cunningham and Bo Leuf
: Rhetorical moves that work well in oratory may actually get in the way in a collaborative space, preventing development and stifling discourse. Since at root, the wiki is not a space for hortatory, agonistic writing so much as a space for deliberative writing, its development would favor rhetorical strategies of invention and deliberation over sermons and lectures.
: But over time, even the most agonistic missive will be moderated by responses and refactored into DocumentMode.
: If you get on a soapbox, expect a response. Expect to be factored out.
: ''Here's a little game I play:''
: ''Write, then delete and simplify as much as possible. Use smaller words. Remove words that add no value. Delete rhetorical window dressing; good rhetoric is not separated from the message.''
: ''When you get good at this, you will find your sense of rhythm will improve and, with it, your rhetorical style. Most sentences sound the best when they are crisp but meaningful. So do Wiki page names.''
: ''You'd be surprised how long it can take me to write a three line post. Sometimes you can watch me edit the same text many times in a row. It takes effort, but it's worth it because the resulting text is clean and crisp. -- SunirShah [http://www.usemod.com/cgi-bin/mb.pl?StyleGuide Meatball Wiki StyleGuide]''
* Civility and understatement give contributors space to work. Namecalling and writing to annoy others spoils the pool. Write to make this a comfortable place to work.
* There doesn't seem to be much profit in writing off the cuff on a wiki - even in ThreadMode. WikiStyle is a thoughtful, crafted style.
* Concision is nobel. Concision keeps the signal to noise ratio up (high signal, low noise), and it allows others to contribute.
* Clichéd thought (yet another iteration of What Everybody Already Knows) contributes little and can get in the way of development. While clichéd thought may be merely annoying in prose, it is a burden on a wiki, increasing noise while contributing little. Have something to say. And on a related note,
* On a wiki, ideas rule. Posing and posturing offer little to development. When the prose is more about the writer than the subject, the writer gets in the way of the ideas.
* Structure the page
* Reorganize the page
* Trim ThreadMode comments to bring the gist forward so others can respond to it.
* Refactor the page to DocumentMode
* Heads and subheads help create structure which helps create meaning. Structure pages using TextFormattingRules.
* Bulleted lists can be AGoodThing. But don't let lists stand in for DiscursiveProse. Use lists as an element of DiscursiveProse.
* ''' Page Summaries ''' We like to use page summaries on this wiki to help others quickly get oriented to the page. Post a page summary at the top of the page, laying out what the page will cover or do. Change the summary as the page evolves. Writers can also use this summary area to list what needs to be done on the page.
: Summarizing the main points of a page can provide a fresh start for refactoring.
* Links: Use descriptive link text and consider where the links might be placed on the page: in line or called out.
* Refactoring might entail finding a PagePattern to help organize the content. Heads and subheads signal the PagePattern.
* Refactor pages to emphasize the structure of ideas, not the chronology of contribution.
* Roll ThreadMode material and ideas into DocumentMode. Recast the prose in a clear, concise, third-person voice, maintaining the ideas but giving them structure.
* A page can be broken up into several pages if the threads seem to become to convoluted and need clarification.
* If you see an infelicity, a typo, a misspelling, fix it silently.
* Edit sentences and paragraphs for concision and clarity.
* http://biro.bemidjistate.edu/cgi/notebook.pl?NotesTowardsARhetoricOfWiki/ComposingProcesses


Revision [115]

Edited on 2006-12-13 12:59:01 by MorganAdmin [Removing unnecessary space]
Deletions:
* pages on Morgan's Wiki
** ComposingProcedure
** Developing_Pages
** DraftingInWiki
** Refactoring_Pages


Revision [114]

The oldest known version of this page was created on 2006-12-13 12:58:39 by MorganAdmin [Removing unnecessary space]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki