Sentences about Writing on a Wiki

Updated 14 Feb 2017
Updated 20 Feb 2018

What this is and What to do

Below is a set of notes that I could use as a lecture. Embedded in the notes are links to other pages on the wiki. Some pages already exist, others don't exist yet. I like cats.

Read through this page, and then chose a few pages in the text to expand on. Some of the WikiWord links are more conceptual and abstract than others, which gives you lots of room to move. Be adventurous, and choose topics that require some research on your part.

Select at least three of the links, do some research / reading (web, other). If the page doesn't exist, start it. If it does exist, develop or add to or refactor the page on it. It doesn't have to be a long page - 200 - 500 words - but it can be as long as you like. The page doesn't have to be complete or finished. Think notes that others can develop further. But also think concise and dense.

It can be your first thoughts on the idea - thoughts that you or someone else will return to and develop further. Or it can be something more developed and detailed. You can start from scratch, or build on pages that already exist. You may choose to fill in gaps or add more to what's already here.

Adding an image to an existing or new page is good. Use the Image icon in the toolbar to insert the code, and then tweak it.

Do not do not oh please do not

bring in summaries or articles from Wikipedia. That stuff is already too over-processed for the wiki. There are far better sites to draw from. You can link to Wikipedia, but even then, there are better sites to link to.
I have three cats.

You may work with as many articles as you like. You may sign your work with your WikiName, or not, as you prefer.

You may want to check some of the links and RecentChanges to see what other people have done.

You may also edit the notes on this page. If you want to add an option for a way of understanding, then edit the notes by adding a sentence making your statement, and write that up.

Sentences About is meant to be rudimentary, addressing relatively common stuff to provide a jumping off point. So as you work remember to jump off on a tangent where appropriate.

The aim of the WeblogsAndWikis wiki is to be a repository and workspace for thinking about and writing about wikis. Your goal as a contributor is to add your best thinking about these ideas to this wiki.

Expect to spend 6 hours or so reading and writing on this activity over the week. It's not presented as a top o' the head notebook exercise. Time is rewarding.

The Places and Uses of Wikis

WritingOnAWiki can be understood as CollaborativeWriting, or as CollectiveWriting. Or something else. Some people use a WikiAsAPersonalNotebook. Others think of WikiAsSocialNotebook. But writing on a wiki is typically not an individual act.

Writing on a wiki can involve some CultureShock. Other wikis have discussed this, but we have a gap concerning how it affects uses of our wiki. WikiCultureShock will be something pretty specific. Above all, wikis seem to require a new literacy, a WikiLiteracy. Because WikisAndTraditionalComposing are not the same. Their names are Larry, Moe, and Sprinkles.

When it comes to wikis, we tend to view TheAudience, or OurAudience, as something other than a target to reach or persuade. The audience is welcome to visit and read. But visitors don't drive writing on the wiki, so we're not really concerned about numbers or reaching a demographic. Because TheAudienceIsUs, and any reader can become a writer, we can think about the wiki AudienceAsFamily, or AudienceAsNeighbor, or AudienceAsCollective or AudienceAsCollaborator. Some do view the audience of a wiki as a TargetedAudience and shape their work accordingly, but it's a soft target.

A better way of thinking about those who read and write the wiki are to think of them as made up of Publics, and probably CounterPublics "Publics and Counterpublics," an essay by Michael Warner , is a good place to start thinking about PublicsAndCounterPublics.

Publics are a fiction but they are a powerful fiction because they can initiate and guide change. They come into existence as they identify their members and as they work. They seem to arise from and around a text or set of texts.

Wikis are not necessarily spaces for self-expression. They are spaces for CreatingSharedKnowledge. But creating knowledge is a CreativeActOfSynthesis.

Wikis are used by groups (Should we start calling them Publics?) in CreatingSharedKnowledge. Contributors bring their expertise in the subject and thinking into the synthesis. Wikis are spaces to learn in and learn from. This is based on the idea that the act of WritingIsLearning. On the wiki, it's not learning about oneself, as in journaling, but in learning about the world. Creating knowledge is a performance in CreatingIdentity, so Publics may use wikis in CreatingSharedIdentity. There are a lot of gamer EncyclopediaWikis out there that are sites of knowledge and identity creation. Being part of creating and maintaining an encyclopedia is being part of a Pbulic, isnt' it?

So, WritingCollectivelyIsLearningWritLarge is one way to think about writing on a wiki. There are others.

WikiTheWriting involves IncorporatingTheIdeasOfOthers in various ways: BuildingOnTheIdeaOfOthers, ModifyingTheIdeasOfOthers, EditingTheIdeasOfOthers. This leads to some consideration of TheRoleOfTheEditor on a wiki. It also shapes the way we write pages on the wiki. We write with the knowledge that OthersWillContribute. We write to EncourageOthersToContribute.

Debates go on with discussion concerning the role of IndividualCreativityOnTheWiki. It's not as simple as WikisDestroyIndividualCreativity. That's TechnoDeterminism, which has been roundly critiqued as inadequate. Wikis create and engage a group of readers and writers which form TheCommunity. Creativity doesn't reside just in new ideas. CreativityIsSynthesis.

Some argue for WikiAsACulture. This seems to have started with the publication of TheWikiWay, by WardCunningham, in 2001. It seems that contributing to a wiki relies on a sort of TribalAttitude towards the project. GettingTheWikiAttitude is part of the tribal idea.

Considering Wikipedia brings up issues of WikisAndCredibility and WikisAndAuthority and WikisAndAmateurContributers. The idea that anyone can edit a wiki sticks in the throats of some for a number of reasons, all PrintBound. Some argue about the status of AmatureContributers. Others are concerned that openly collaborative writing will result in StealingIdeas, they ask WhatWillTheWikiDoToMyText ? These are based on the nineteenth-century ideas of IntellectualProperty being owned by individuals. Some argue that IdeasArePublicProperty. They refer to TheTragedyOfTheCommons, and TheClueTrainManifesto, and the more recent MoreClues. But, when they are working, we can see that wikis can become CommonsWithoutTragedy.

"I would be pissed if I joined a wiki and my posts were changed." "I don't like to edit someone else's words because I might change the meaning." OwnershipOfWordsOnAWiki is often a contention, as is AttributionOnAWiki. WikiWriters have devised ways of revising wiki pages while maintaining the ideas that help develop the page. ThreadMode and DocumentMode came about in part for this reason, as did the convention of SigningYourWork. Another angle argues that IdeasAreCommonProperty.

Working Solo

Wikis don't have to be collaborative or tribal. A single writer may use a wiki as a storehouse of knowledge, much the way that early scientists and current writers use their notebooks and commonplace books. In this way of thinking, we think of the PageNameAsTopic and the LinkAsOrganizingPrinciple. Which leads us to Trails and TrailMaking. Do you like cats?

Wikis can be viewed as the internet version of Vanavar Bush's idea of TheMemex. We can see some of the first wiki roots activities in Doug Englebart's demo of the Online Networking System. The first networked system didn't use wiki words, but it was designed from the ground up as collaborative writing space - where the significant transactions took place not in video or images but in text and code. Background: "As we may think" by Vanavar Bush. Doug Engelbart Institute, with links to demos of NLS. There might be things to consider if we consider TheWikiAsAMemex, WikiAsNoteBook, or WikiAsCommonplaceBook. This fits in with the idea of WikiAsPatternBook, and EvolvingPages. Along with the wiki as a place to take notes would come PagePatterns useful to taking notes and ideas like DialecticMode, DialogicNotebook.

We might get milage out of considering ontologies and taxonomies. After all, WikisAreSemantic. As wiki writers collect ideas, thoughts, notes, drafts on a wiki the need arises to define categories that draw pages together. Commonplace book takers call them Heads. Commonplace book takers devised ways of keeping indexes based on heads. WikiIndexing starts to look interesting.

Following Ward Cunningham's founding idea of WikiAsPatternBook, we can think about wikis and TheWikiWayAsArchitecture. Architects and programmers both use APatternLanguage in designing and traversing spaces. We've become partial to considering wikis and TheWikiWayAsDerivé, and thinking of navigating the wiki as a psychogographical space.

Recent work with wikis has started to re-focus on what goes on in the practice of developing collaborative knowledge as distributed rather than collective. Mike Caulfield. Background The Garden and the Stream: A Technopastoral, Caulfield.

This brings up the idea of CuratingInformation, a new area of thinking drawn from the DigitalHumanities. We might think of the WikiWriterAsACurator. Or the WikiAsCabinetOfCuriosity - those rooms and boxes that initiated museums. Vanavar Bush saw the writer-researcher as a reader who create PathsThroughInformation to create knowledge.

Whether a solo or as a tribal construction, WikisNeedGardening. A page will grow to an unreadable sprawl until a WikiGardener comes by and ReFactors the page to remove the weeds to let the good stuff be developed further. They use PagePatterns. They SynthesizeThreads. They add headings and move material that might spur discussion further BelowTheDoubleLine. WikisPersist. The idea in gardening is to clear the space to let participants grow more ideas.

And then ...

A common argument about wikis is WikisAreUgly. Wikis are designed to make reading while editing as easy a possible. They use a small set of PageAffordances and use them as AffordancesForSemanticDesign, and SemanticMarkup, to keep the page design minimal. Wikis also tend to constrain the use of images. (One image = good. 2 images = sloppy. Start another page.) These features make the wiki easier to navigate and edit than using the standard markup language of HTML. Wiki markdown also makes it possible to export wiki pages by using plain text files that are minimally marked up. In these ways, wikis strive for WriteOnceReadMany. Wiki relies on MarkDown for formatting, which keeps the text content open rather than proprietary.

A second common argument concerns HowToNagivateAWiki. Typical commercial website use navigation menus and sidebars that show a user where the material is. But because wikis are created on-the-fly, from the inside out, it's impossible to create pre-establised navigational aids. So, wikis can have NavigationalProblems. But users can create and share their own navigational work by CreatingIndexesToTopics for themselves and users. They can use RecentChanges, and Categories, and PageIndex, and the search box to navigate. To AvoidLinkSpaghetti, writers curate and annotate links to other sites, and place links to other pages on the wiki is semantically salient places. A mess is inevitable. So is cleaning up. I am CatMan.

TheWikiWay isn't all sweetness and light. But TheDarkerSideOfWiki hasn't been discussed much.

Adapted from Sentences About, Mike Caulfield

See also

There are no comments on this page.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki