[drupal-docs] New book about Drupal?

[Charlie Lowe]

I want to echo Kieran's concern here. Drupal prides itself on being the
CMS that will readily revise important core features between versions in
such a way that a book for developers on coding or one with a larger
audience that focuses too heavily on features will be out of date within
six months after it is published.  Creating a book which lets people see
the types of projects that Drupal can support, the changes that those
projects have brought to the project (and thus a vision of the future),
and anything that explains conceptually how to think about Drupal (i.e.,
how to wrap one's mind around taxonomy and the node system) is likely to
have more staying power and be time better spent by those doing the
writing. Keep the parts of understanding Drupal that are a moving target
in the Drupal handbooks. To think print, think longevity.


Kieran wrote,
>
> If you write a page about the event module, how will you explain to
> the editor that event module is getting a patch every few days.
> You'll get blasted when the book comes from the printers because it
> will be wrong.  In the future, I'll be walking along in the mall and
> see the book in the $0.99 store.  Wow!  Drupal 5.7, that's so old, I
> can't believe we actually had to use that stuff.
>