On Mon, 12 Mar 2007 14:14:30 -0700 mpb <[EMAIL PROTECTED]> wrote: > Step 1) Identify user groups. > > Different types of users will want different information from the > Wiki. I see 4 different types of users. There may be more. > > * Potential users > * Beginning users > * Advanced users > * Gobo devel team
I'd merge Advanced users + Gobo devel team, unless there's a special reason for this separation. :) > Step 2) Define the goal of the Wiki. > > As I see it, the goal of the Wiki is to: > > a) help potential users efficiently decide whether or not to install > Gobo > > b) help begining users efficiently become advanced users > > c) help advanced users improve Gobo (via bug reports and recipe > submissions) and customize Gobo to their specific needs But this would be done at the wiki or the wiki would provide extensive documentation of these procedures? Ie, details about how to report clearly a bug, how to create recipes and how/where to submit, and how to adapt Gobo to their need? > > d) allow the devel team to focus on development rather than support, > and serve as a reference for how things should work > > Some of these goals overlap with the web site, which is why I am > interested in creating a consistent user experience across the two of > them. As I understand, the website becomes news-oriented while the wiki becomes (deeply) content-oriented, in such a way that whenever the user faces something odd or new, s?he simply refer to the wiki. More or like what the FreeBSD Handbook is (you start googling around if you didn't find what you're looking for in the handbook, but it is always your first try). > Step 4) Match content categories with user groups. > > Beginning users need documentation that provides reasonably complete > context. Advanced users need much less context. The style of and > amount of context provided by each page must match the needs of the > target users of that page. > > The following sections should target potential users: > About Gobo > Community > (and to a lessor extent:) > Platform specific pages (does Gobo work on my platform?) This one I think it's *very* nice, and may further include oddities (like "card xxx does not work with 012") that usually makes new users panic and switch back to anything else they were using. > Handbook > > The following sections should target beginning users: > Handbook > Platform specific pages > > All other sections should target advanced users and the devel group. I must ask about additional info about the distinctions between advanced users and devel. The way I understand, devel are advanced users. > Step 5) Impose category framework > > My plan is to explicitly categorize every page in the Wiki into the > following MediaWiki Category hierachy (in alphabetical order): > > > About Gobo (currently 5 pagse) > > > Community (15) > | > +--> Discussions (22) > | > +--> Roadmaps (?, currently mixed in with Community) I wouldn't have found Roadmaps under Community. :) Doesn't it worth a Development category, which may further include info about the previous releases (what they had packaged in), and what's being considered for the new ones (alongside the roadmap itself, which usually provides a not-much-detailed big-picture of the coming releases)? > | > +--> WikiTeam (22) > | > +--> Redirects (5) > | > +--> Maintenance (0) > > > Documentation (0) > | > +--> Handbook (45) > | > +--> Howtos (25) > | > +--> Platforms (5) > | > +--> Reference (97) > > > Trash (was 37, currently ?) > | > +--> Spam (was 7, currently ?) No additional considerations about these. :) > Step 6) Write and enforce WikiTeam policy guidlines. > > The guidelines will be very similar to the contents of this email. > They will tell content contibutors and volunteer members of the > WikiTeam how the Wiki should work: that pages must belong to > categories, that the style and content of pages must target the > appropriate user group, etc. > > The goal of the policies to allow everyone to move the Wiki in the > same direction, and to make that direction readily apparent. Definetely, or there will be chaos. :) > Step 7) Implement maintenence tracking techniques > ... > This page [[Last Reviewed March 2007]] at Scripts version 2.6.2 by mpb. > > This will allow tracking (via back-links) of when pages were last > reviewed, and will allow older pages to be reviewed and updated first. Is there an automated way to do that or will require explicit information by who is updating it? > > Create a Todo page. Any page that needs work done should link to the > Todo page. This will make it easy (again via back-links) to see how > many pages across the whole Wiki need work done. This is a must. :) Seems like the wiki will get much better, given the amount of effort you already invested in it. Congrats! -- Ricardo Nabinger Sanchez <[EMAIL PROTECTED],wait4.org}> Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
