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

[Robert Castelo]

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.

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.



Best regards,

Robert