<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: [documentation] Role Based User Handbooks</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText79852 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Same problem..... who
volunteers to read the queue? I understand <FONT
face="Times New Roman">Bčr's re-phrasing of this better now and it's a neat
theory. Who monitors the queue? And then where is the
information displayed? Who chooses and sets up guidelines? How do
they decide what for their personal blog and what for their Drupal
blog?</FONT></FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Again, neat idea, needs more meat as currently I don't
know if we have enough people currently monitoring the moderation queue as it
is.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> documentation-bounces@drupal.org on behalf
of Bčr Kessels<BR><B>Sent:</B> Thu 1/12/2006 2:11 AM<BR><B>To:</B> A list for
documentation writers<BR><B>Subject:</B> Re: [documentation] Role Based User
Handbooks<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Op donderdag 12 januari 2006 03:22, schreef Boris Mann:<BR>>
Again my plea is to turn on the "story" node type and have this type
<BR>> of info be able to be submitted by anyone, go into a submission
queue <BR>> and get approved. We'd have a nice, categorized archive
(free <BR>> tagging, of course, perhaps with some additional "big
buckets" like <BR>> Tips, Best Practices, Recipes, Case Studies,
Official News, etc.) and <BR>> a way for anyone to get exposure by
writing good content.<BR><BR>We, down at sympal ar experimenting (in Dutch) with
this type of<BR>handbook/information. its not public, yet, so i will explain the
idea and<BR>plan:<BR>* A few people blog. Add random articles on a random
topcis, with random skill<BR>levels.<BR>* We tag these articles. Freetagging,
but not too free.<BR>* Once in a while we reorganise that loose information into
books. If there is<BR>enough to fill a chapter, that is.<BR><BR>I visualised
this as a line of articles passing by (the blogs), which one can<BR>filter,
based on his or her preferences (feeds per tag) and wich;, at the end<BR>of that
line is sorted into nice piles.<BR><BR>Funny to see that Boris proposes this
same structure for Drupal.org. I<BR>definately like the
idea!<BR><BR>Bčr<BR><BR>--<BR>| Bčr Kessels | webschuur.com | website
development |<BR>| Jabber & Google Talk: ber@jabber.webschuur.com<BR>| <A
href="http://bler.webschuur.com">http://bler.webschuur.com</A> | <A
href="http://www.webschuur.com">http://www.webschuur.com</A> |<BR>--<BR>Pending
work: <A
href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</A><BR>List
archives: <A
href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</A><BR><BR></FONT></P></DIV>
</BODY>
</HTML>