[documentation] Re: Cleaning up the about section of the Drupal handbook

[Kieran Lal]

On Feb 11, 2006, at 7:55 PM, Robert Castelo wrote:

> I'd like to change the title of "Overview for professional Drupal  
> site developers" back to "Overview for consultants".
>
> The idea of the page is to help consultants fill in requests for  
> tender and hopefully win more contracts for Drupal based projects.

The general feedback at the conference was that consultants is  
impossibly vague.  I have no personal opinion one way or another, but  
responded to very clear and distinct feedback.
>
> Consulting and developing are two distinct roles. Yes, some  
> consultants code, and do design work, but those are three different  
> skills, which we should document separately.
>
> Consultants deal with clients, they require a knowledge of what  
> Drupal can do, but not necessarily how it does it. By that I mean a  
> consultant needs for instance to be able to present data which  
> proves Drupal is scalable, and be aware of features which improve  
> scalability, but they don't need details of how to make it scalable.
>
> The rule for what goes on this page should be "can I present this  
> to a client?". Stuff that a client doesn't need to know can be left  
> out.
>
> Leaving the title as it is risks turning this page into a site map  
> for the development handbook.

Go ahead and change at will, but I think you need to qualify  
consultants.

Overview for consultants who advise clients on the use of Drupal or  
something like that.

Kieran

>
> Best regards,
>
> Robert
>
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>