Chatfield Wikis Chapter 7 Reading Notes

CHATFIED - CHAP 7
#############CHAPTER 7##########################
#############CHAPTER 7##########################
-WIKI STRUCTURE AND ONTOLOGY -
-organization vital
-author should give decent definition of ontology if he wants to discuss it.
-decide navigational structure
-visual aspects, themes, colors, skins -
-clear visual idea.
-BASIC STRUCTURE AND LINKING =
EFFECTIVE STRUCTURE-
-analogy spiderweb -
-analogy Internet -
-gotta know exactly how site to look before adding content.
-important cuz gonna relinquish control and wanna have basics in place.
-big mess after new members get done.

ONTOLOGY AND STRUCTURE-
-categorize info - EXACT FIT
-so, sit down and figure out how many diff categories, page types and directions gonna go.
-break all down like biology - kingdom, phylum, class, order family,genus, and species
-gotta have smaller subsets that break down and gotta organize so are not messing up navigation or doubling topics.

1. Natural groupings - films into director and genre
-books by author
-music by album or artist
2. Charts - detailed and well-organized.
-maintain few key details from top of chart to bottom
3. Actions - categorize tasks that need to be accomplished by location in hierarchy of tasks ea person needs to do.
4. Alphabetical - simplest
-before using, consider how visitors will expect to find content - use more reasonable be4 this.
5. Space and Time - deadlines of tasks - Mon, Tues, Wed
-tasks done by specific dept.
6. Location - breaking down geographcially.
-works for some.

Patterned Linking-
-directly concerns how people who visit will interact w/ the info.
-no long strings of diff categories
-set a few and have smaller pages in them
Easy linking -pages connect using simple linking structure w/ "[[link]]" tag.
-gotta use and integrate so none broken - can't sent to places don't exist.
-CREATE STANDARDIZED FORMAT TO NAME PAGES SO REMEMBERED AFTER COUPLA USES.
-can shorten name/link that appears on webpage.

-CREATING NAVIGATION STRUCTURE -
-decided format to break down content, now make paths to lead thru wiki to info.
-what links put on front page
-what links on support pages.
-what links on content pages.

-FRONT PAGE - SHOWCASE CONTENT
-GIVE WAY TO NAVIGATE THRU CONTENT
-need direct method to get to another point via front page
-gotta link vital points in wiki
-but can't overdo…..how clear can this idiot be? do it - but don't do too much -vital -but not overdone -moron.

-WHO IS AUDIENCE?
-if content, advertise for content
-give links to most valuable content
-provide walkthru how/where to add content
-process wiki diff - oranization and access - list all projects
-community wiki focus on showcasing interests and fields of study.
-Chatfield is Rettberg Jr.
-front page - draw in , ask for content, provide links/paths to navigate
SECTION PAGES
-next is section pages
-people use to browse for content.
-see what is here and what isn't - plug into right location.

NAVIGATION TOOLS
-series of nav tools -
-appear on every page-
-HEADER AND FOOTER - proved architecture of the page currently being viewed.
-includes parent categories or sections and path back to main page.
-SIDEBAR - more detailed version of top and bottom bars
-or offer related pages
-search options
-login info
-stats about present page
-HEADERS-
1. breadcrumbs - need if using wiki to gather info
-where the come from on diff pages
-how get back to orig category
2. tags - show which categories or tags related to page being viewed.
3. searchbox - top right corner - allows for quick and easy access to the search function.
4. jump boxes - tabs at top right or in middle and takes user to pages for editing, attaching, printing, or logging in.

-FOOTERS-
-same links as header but broken down more specific categories.

-SIDEBAR-
-diff uses -examples
1. -Support pages - liks to support pages of wiki including documentation of software, current editing guidelines, help files
2. -FAQ's frequently asked quesitons - forum to ask questions -
3. -Search - search box or forum users can access and direct content w/ click of button
4. -recent changes - provide list re: whole wiki or current page
5. -newsletters/notifications - way to sign up and get e-mails whenever change made to wiki, wiki altered, or wanna invite back
6. -subscriptions - w/ RSS feed

VISUAL CHANGES-
-visual bump -
-color - funtionality
-divide page into diff sections
-THEMES AND SKINS - easiest way to change look
-provided in software-
-no. ways can use colors and images - gotta have good reason to do these though.
-if add color and images, make sure adding value to page
-TEMPLATE USE ON WIKI -
-good tool to show what's prefered and been done before
-consistency

-make easier to use
-make better looking
-make so gets more visits thru search engines and outside linking …..