On Thu, 2009-07-16 at 15:02 -0700, Karsten Wade wrote: > Great! We are seeing a lot of interest in using the wiki for writing > general-purpose how-to documentation. > > I wonder ... would it be useful for people to read fedora-list, > fedoraforum.org, and talk with moderators on #fedora about common > issues, then turn those in to short articles on the wiki? The next > thing is, of course, to post back to that thread (email, forum) with a > link to the new canonical wiki source for that answer. > > We were talking earlier today about a knowledge base (kbase). That is > another great idea, focused on much shorter articles to solve a > specific problem. While that is being researched, why not start > writing content in to the wiki? > > It would be a good idea to add a category at the bottom of each > article, such as: > > [[Category:Kbase article]] > [[Category:Kbase article draft]] > [[Category:Kbase food]] I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten thousand tiny pages' school of documentation. It winds up with two major drawbacks: you can't ever find anything, and nothing gets updated. (Visit the Gentoo wiki to observe both in operation). Most issues that are encountered on #fedora or forums, for instance, should be documented in either the Common Issues page, or the Release Notes. This was mostly what my earlier (long) email to the list was about, which no-one seemed to reply to. I really think it's better to keep things in some semblance of organization in central, canonical pages, rather than having zillions of single-issue pages... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
