[drupal-docs] Drupal vs Mambo

[Charlie Lowe]

>
> Laura Scott wrote:
>
>>  In other words, focusing on what Drupal can do for the person who
>> knows nothing about Drupal (and you may have noticed that even the
>> vast majority of slashdot geeks had never heard of it in the
>> fundraising thread a few weeks ago) rather than pointing out the
>> specs.
>
>>  Parallel: You can sell a car by talking about features -- what size
>> the engine is, what rating the tires have, and so on. Or you can sell
>> a car by talking about benefits -- what it does for you, how easy it
>> is to use, and so on. Both are valid, but the "benefits" side could
>> use some fleshing out, it seems to me.
>>

Liza replied:
>
> Great point Laura, and to expand on that,
>
> It's the difference between communicating a product as a world of
> possible outcomes (target markets) vs. presenting a product as a to-do
> list (features).
>

+1

Some random thoughts:

What's interesting to me about this approach is when creating
documentation, the goal is to help the user to complete a task, to take
action. Benefits/possible outcomes are about portraying Drupal as the
result of configuration of features. This is important because we
constantly see in the forums questions about can Drupal do this, can
Drupal do that. Feature lists can't address those questions; but
describing potential end uses of Drupal can.

Also, the benefits discussion can be linked to the case studies page
(however, "case studies" is, IMHO, a clinical term; there must be
something better). Or perhaps, the main case studies information is merged
into what Laura was describing.