[drupal-docs] Handbook v2
Moshe Weitzman
weitzman at tejasa.com
Sun Mar 20 03:12:12 UTC 2005
This reminds me that MediaWiki (i.e. Wikipedia) has a great model for
discussion of pages. They show comments on a tab, instead of below the
article itself. Makes a lot of sense for book pages, and possibly other
node types. For example, see
http://en.wikipedia.org/wiki/Talk:University_of_Oxford
On Mar 19, 2005, at 6:16 PM, Ron Mahon wrote:
> Why not use the forum to have the discussions on any changes to the
> books
> instead of the comments.
>
> That way you still get the interaction of all types of people expert
> and
> novice. Just a simple link to the forum maybe "Discuss this Page".
>
> Preserves the best of both worlds and doesn't isolate any one.
> Ron
>
> InterNet Marketing Resource Center
> A Free Super Mart of Articles, Demos, Tutorials everything you need to
> Succeed on the net.
> www.inmrc.com
>
>
> -----Original Message-----
> From: Boris Mann [mailto:borismann at gmail.com]
> Sent: Saturday, March 19, 2005 3:44 PM
> To: drupal-docs at drupal.org
> Subject: [drupal-docs] Handbook v2
>
> OK, after I made enough of stink, we got to a consensus, sort of.
> Comments are another issue which we can't solve right away, but which
> we can
> police a lot more effectively as we build up new pages.
>
> I've written up extensive thoughts here:
> http://dev.bryght.com/t/wiki/HandbookVersionTwo
>
> It includes book technology suggestions. Please add/edit comments
> there.
>
> On 18-Mar-05, at 12:11 PM, Dries Buytaert wrote:
>
>> OK, it appears there are a number of issues here. To summarize:
>>
>> 1. The documentation sucks: people don't find the information they
>> need.
>> 2. The process to maintain documentation sucks: documentation writers
>> don't know what is going on.
>> 3. Poor separation between user and developer community.
>>
>> We want to tackle (1) by reorganizing the handbook from scratch. We
>> need to tackle (2) by improving Drupal itself, and the book module in
>> particular (or by using CVS). There are different ways we can tackle
>> (3).
>
> I actually don't see (3) as too much of an issue. Or rather, that we
> can
> serve both communities by my suggested hierarchies, and perhaps some
> guidance on the front page of Drupal that points different user groups
> to
> appropriate channels/an intro page.
>
>>> Here's an alternative that MIGHT work: give us a new root book --
>>> call it handbook v2. The doc team can decide how best to organize
>>> this, and migrate external and local pages into it. It's still
>>> starting from scratch, but it retains node IDs.
>>
>> That works for me. We'd still need to deal with 2 and 3 separately
>> though.
>
> --
> Boris Mann
> http://www.bryght.com
>
>
>
> --
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
More information about the drupal-docs
mailing list