[drupal-devel] A collection of usability problems

[James Walker]

On 23-Sep-05, at 4:51 AM, Dries Buytaert wrote:
> On 23 Sep 2005, at 10:44, Gabor Hojtsy wrote:
>
>>> Problem #2: many people use the book.module to create structure.   
>>> The
>>> book.module is a logical choice <strong>if and only if</strong> you
>>> know Drupal.  If you're new to Drupal, creating structure using the
>>> book module is not exactly logical.  The underlying problem is that
>>> people need a way to link pages and to create structure.  Simply
>>> renaming the book.module to outline.module or structure.module and
>>> dropping the book node type might come a long way for new users, and
>>> might help focus development efforts.
>>>
>>
>> This was suggested before, and it would be a good improvement IMHO.
>> Outline module is the way to go!
>>
>
> There was consensus but the problem was that it requires the book  
> node type to be dropped.  This breaks some people's workflow /  
> permission scheme.

I don't think there's any reason you'd *have* to drop book.module -  
it could become another "simple node type" - to maintain backwards  
compatibility (what? what's that?) ... but breaking out an  
outline.module still makes sense to me (yes, as we discussed i think  
first in February?).

The thing is the "online handbook" idea has attracted a lot of drupal  
users... but a generalized outliner would as well (that would still,  
of course, be used for book organization).

--
James Walker :: http://walkah.net/