First off, very well thought out. You put a lot of time into this. Thanks a lot.
On 3/12/07, 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 don't think it worthwhile to breakup the user types further. Keeping it simple is best from a maintenance and navigation standpoint. > > 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 > > 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. > I completely agree with a+b. c is outside the scope of a wiki. ArchLinux has an interesting webtool for that. See [1]. d will improve with a-c. [1] http://aur.archlinux.org/ > Step 3) Identify content categories. > > As I see it, the content categories, ordered from most pages to least > are: > > Pages Category > 97 Reference pages > 45 Handbook pages > 37 Trash pages (many already deleted by Nick) > 25 Howtos > 22 Discussions > 16 Users pages (some deleted by Nick) > 15 Community pages > 8 Archive pages (of historic interest) > 7 Spam pages (possibly now deleted by Nick) > 6 "WikiTeam pages" that discuss wiki policies, goals > 5 "About Gobo" pages > 5 Platform specific pages > 5 Redirect pages > 3 ??? (I cannot tell what these 3 pages are.) > 2 Floater pages that need to be merged with the pages they support > Way too many categories. For instance. Handbook and Howto could probably be merged. What are Community pages? Regardless, good start. The actually categories can remain somewhat fluid during the rework. > Step 4) Match content categories with user groups. > Seems reasonable. Again much of it is related to first step. > Step 5) Impose category framework > Good. > Step 6) Write and enforce WikiTeam policy guidlines. > > The goal of the policies to allow everyone to move the Wiki in the > same direction, and to make that direction readily apparent. > Excellent. This is really needed. > Step 7) Implement maintenence tracking techniques > > In the Community->WikiTeam->Mainetance category, create the following > pages: > > Last_Reviewed_<month>_<year> > > Each page in the wiki will link to the appropriate "Last_Reviewed_..." > page. > > For example: > > This page [[Last Reviewed March 2007]] by mpb. > > Or: > > 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. > > 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. > > These tracking techniques will also allow multiple volunteers to cooperate > indepenently. > I'm not familiar with these techniques but they sound good. > Step 8) Streamline Wiki navigation so that it targets beginning users. > > Among other changes, this may involve merging some handbook pages > together to make navigation for beginning users more linear. Entry > pages and table of contents pages will also be streamlined so the > focus on beginning users needs. > Agreed. the wiki should be focused on the beginning user. Advanced users should be ok with an index to the reference pages. :-) > > As always, comments and suggestions are welcome. I'd like to get > feedback before investing serious time in editing the wiki. > > Thanks! > You've done a great job analyzing the current state and outlining a way forward. thanks. Based on the feedback of this thread you should develop step 6 (the wiki guidelines) further. Then post to the user list for additional comments and recruit volunteers. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
