Guide to Using This Site

CleanCutRogue's picture
September 28, 2007 - 1:39pm
I was thinking about how to organize a guide to using this site.

Idea 1 - one guide containing the following:
  • A discussion of the basic organization of site content (a brief explanation of the site's organization).
  • A layout article describing things on the site and what they mean (the various menus, the online indicators, the tabs, you know, basic things to be seen/interacted with... complete with screenshots and balloon text and arrows).
  • A disussion on standards and practices complete with notes on site rules.
  • A how-to on the more advanced features of the site (usage of tags, etc).

Idea 2 - two guides (basic and advanced):
Subsequently I've thought it should be two guides: a basic (the first three topics shown in Idea 1) and an advanced (the last topic).

Idea 3 - Three guides divided into content types:
The site has three conceptual types of content:
  • General Content (project lists, userlists, forums, chat, links, feedback, and support issues)
  • Project Content (each with its own: front page, forums, documents, downloads, membership, and support issues)
  • User Content (each with its own: profile, private messaging, guestbook, quicklinks, buddy list, contact form for email, and storage space for personal files).
Perhaps therefore there should be three guides, one for each one of these, complete with layout/advanced notes for each topic?

But then I keep asking myself... are all these really necessary? Use of bulliten boards/forums and community sites are a fairly intuitive thing nowadays.

But this site is doing some things that (from what I've found) no other site does. That makes me think there needs to be a guide on Project Management - showing all the rules for a project manager that aren't available to the members of his site (such as cancelling and banning members, censoring, addressing project support issue status and severity, and the various uses of the many options now present when editing the options for your project's front page). Should there be a project management guide?

Finally... if one or more of these guides are to exist - who's going to maintain them? It sounds like a lot of work, and maybe would be better done as its own wiki-like project where all of us can work on it.

What do you all think?
3. We wear sungoggles during the day. Not because the sun affects our vision, but when you're cool like us the sun shines all the time.

-top 11 reasons to be a Yazirian, ShadowShack


Anonymous's picture
Corjay (not verified)
September 28, 2007 - 4:32pm
I prefer idea number 3, except that profiles should probably come with their own guide entirely, because of all the functionality in them. w00t has volunteered himself to do video presentations, so let's see what he can come up with.

w00t: ask all the questions you need. But this will also require that you become as proficient with this site as anyone, including with profiles.

Rum Rogue's picture
Rum Rogue
October 2, 2007 - 1:12pm
I hate to sound like a copy cat, but I agree with Corjay.

One thing to remember, is that no matter how well written it is, there will always be someone who just skimmed it and wont understand.
Time flies when your having rum.

Im a government employee, I dont goof-off. I constructively abuse my time.

Anonymous's picture
w00t (not verified)
October 2, 2007 - 1:22pm

I will do one simple video to test and see if that is what we want.
We could use someone who has never been on the site to test)

Corjay, can you help with the documentation to support the video?

What topic should I tackle first?

Anonymous's picture
Corjay (not verified)
October 2, 2007 - 1:34pm
I'm better at research, compiling, rewording and only filling in blanks. I would prefer somone else come up with the details, at the very least to give me a framework from which to operate.

The brainwork required for this is going to be substantial, and right now i'm trying to get the 25th Anniversary Edition Rulebook out while it's still 2007.