Drupal 7 book coverFollowing the success of its predecessor, Building powerful and robust websites with Drupal 6, Packt Publishing announces Drupal 7, an updated and revised version of the original book by David Mercer written specifically for Drupal 7. The book is written for Drupal 7 beginners or newcomers to Drupal in general and will help help anyone to create and operate any type of website quickly and efficiently.

This book provides a great way to learn and master Drupal 7, enabling you to create virtually any type of website. It meets the booming demand for well presented, clear, concise, and above all practical information on how to design and build sites like a pro. By clearly and concisely demonstrating the fundamentals of Drupal in combination with practical and methodical coverage of more advanced subjects, this book paves the way for anyone to quickly become proficient at building and operating professional websites.

150 quiz questions and exercises will help you to consolidate and expand on what you learn in the book.

Drupal.org readers are also entitled to a 20% promotional discount when ordering through Packt. Make sure you provide the discount code (Drupal7book20) upon purchase to receive the discount.

Remember that, as with all Packt books, a percentage of the revenue from each book sold will go to support the open source technology on which the book is based - in this case, the proceeds will benefit the Drupal Association.

What you will learn from this book

How to:

  • Plan and consider various design aspects of your site
  • Install, set up, and configure a Drupal development machine
  • Find your way around the vast array of Drupal settings with ease
  • Add and work with modules to enhance your website's functionality
  • Control and manage content
  • Master content layout and display with Views and Panels
  • Work with any type of media
  • Deal with security issues, users, and access control
  • Implement a customized interface for your website
  • Add powerful new features and learn advanced techniques
  • Deploy, manage, and maintain your website

From the author

It's a testament to the vastly improved usability of Drupal 7 that I was able to substantially condense the introductory material, expand on the more advanced topics and introduce exciting new topics. This latest incarnation of my series of Drupal books, while still firmly aimed at beginners, tackles a wider range of topics and does so in more depth. For example, Views gets its own chapter, as does media, the theming chapter has been completely rewritten to include stuff like template overriding, and all the new goodies that come with Drupal 7 are covered.

In effect, the improvements to Drupal 7 itself have allowed me to make corresponding improvements to the new book.

This time round, I've also included a whole bunch of marked online quizzes (to test your knowledge) as well as plenty of online exercises (to help expand on what you learn in the book).

If I've done my job right you should find this book not only provides a solid knowledge base, but also turns you into an adaptable and resourcesful webmaster who can accomplish just about anything.

Praise for David Mercer's previous titles

This is one of the best book purchases I've ever made! After struggling to find good online tutorials that cover the basics well, I found this book. I feel confident that, by the time I work my way through this book, I will have a working proficiency with Drupal and can begin to build my own feature rich sites. - Jay

This is a good book to read even if you read Drupal 5 by the same author/publisher. It is a beginning level book but covers the new features nicely. This book assumes you do not know HTML or PHP. - David A. Shaver

This book has been wonderful. It is well versed and easy to understand. It gives the basics on Drupal and I would recommend this book to anyone who wants to set up a Drupal site. I am impressed with the author's ability to break down the basics in easy to understand sections. He takes it one step at a time and makes it easy to copy and initiate each section with lots of illustrations and hints. - R. Todd


Dave Reid’s picture

But I'm curious how exactly were Views and Panels covered?

Senior Drupal Developer for Lullabot | www.davereid.net | @davereid

SME Pals’s picture

Thanks Dave,

Including Panels was a tough decision for me. I think it is important for newcomers to be aware of what they can achieve with them. As you no doubt know, Panels weren't available in alpha or beta at the time of writing (unlike Views). So, I wrote to Sam and asked him what he thought regarding Panels and D7. His response:

... we're anticipating as straight of a port as possible, so it should be safe to assume that the 7.x featureset will be pretty much the same as the 6.x, at least initially.

Now, I appreciate that things may change, but on the strength of this reply I decided to go ahead and give Panels some coverage. Not much, but enough to show people what they are and how to begin using them should they decide to use them.


merlinofchaos’s picture


Can I just assign every issue generated in the Panels/CTools queues to you, then?

Panels & CTools are not yet available *at all* for D7, but your book is available now.

Seriously, it's bad enough that there's all these books being published about my software without me being consulted at all, but now they're being published known to be wrong.

-- Merlin

[Read my writing: ehalseymiles.com]
[Read my Coding blog: Angry Donuts]

Juliancpackt’s picture

Hi Earl,

My name is Julian Copes and I work at Packt - amongst other things, I work closely with Open Source projects, including Drupal.

Thank you for your thoughts on this and I appreciate your frustration here. As commented above, David Mercer got in touch with Sam Boyer, who has over a thousand commits to the Panels project, to ask him about it. With the knowledge that things would be subject to change, David gave this important topic only a very brief coverage, and a note at the start of the section informing readers that this particular topic was written without the D7 version – it will be very clear to readers what this information is applicable to. David is currently on holiday but will explain in greater detail once he is back.



greggles’s picture

What was the response? Was it "This is a great book!" or was it "Hmm...don't publish this."

CARD.com :)

yautja_cetanu’s picture

I'd probably ending up getting a book like this just cause I love books... however I'm interested (I feel like I like packt). Are there many books that cover views where the author has contacted you and you'd recommend? Or would you just recommend the advanced help handbook?

So far reading the book using drupal has been awesome

SeanBannister’s picture

No worries Earl, they'll release a patch for the book once Drupal 7 is released. They're taking chasing head to a whole new level ;)

jcnventura’s picture

From what I can see, you'll be able to download the errata from:


How do you apply a patch to a paper book? Scissors and glue?

João Ventura

rj’s picture

Yeah, literally. With Apress, you release the initial print edition and then write follow-up chapters and revisions that are released through their website, preferably as the software/framework changes.


SME Pals’s picture

My apologies for the delayed response - I was taking a much needed break. With regards to my decision to give Panels coverage in this book, I'd like to point out the following:

I have developed and moulded this book to be as useful as possible for beginners to Drupal. It's basically a book covering everything I would want to know if I was starting out again. I personally consider Panels to be a project of such importance, that despite it not being ready for D7 at the time of writing, I felt it necessary to at least mention it.

Accordingly, I plastered a huge warning in bold font at the top of this particular section warning readers that this was written against D6 and is subject to changes.

The lion's share of what little coverage this topic received revolves around what Panels are, what they can do and how they can be used. This material is effectively version agnostic and doesn't rely on the code being operational. Its intention is to make beginners aware of this powerful tool and understand what it can do sufficiently to make an informed decision when it comes time to develop their own site. If I've done my job properly, the practical coverage and tuition provided throughout the book will give my readers the skills and flexibility to implement Panels if, as and when it becomes available.

I'd like to close by saying that while I acknowledge that flaws exist in the publishing world, I personally do my best to create a truly useful book that contributes to the growth and (hopefully) the popularity of the project concerned. I have over ten years of experience in writing (on PHP, Linux and open source technologies) that I draw upon whenever I create material and I firmly believe that my readers benefit from what I bring to the table - otherwise, I wouldn't do it.


Wolfflow’s picture

+1 @merlinofchaos

To the announcement: Guys really this is a .... how can express my astonishing about being so interested on making money on behalf of others work and years of contribution to Drupal. How can "Who ever was" start to put this weird announcement on Drupal.org front-page before D7 is out and stable? I really do not understand what the hell is happening.

[Point the finger: Assign Blame!]

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

davideads’s picture

Does anybody really take Packt publishing seriously, except for the people who promote stories to the d.o home page? I know they may have some good titles, but that's sort of like saying a perenially losing team in pro sports has some good players. It seems like shameless, depressing money-grubbing -- but with the potential to alienate and confuse noobs while anybody who knows better will simply ignore.

Juliancpackt’s picture



My name is Julian Copes and I work at Packt - amongst other things, I work closely with Open Source projects, including Drupal.

Support for Open Source, and specifically projects such as Drupal, has been central to what defines Packt, from day one. We are proud of our support for Open Source and the launch of our dedicated Open Source brand demonstrates this commitment. Just recently we have passed the milestone of donating $300,000 to Open Source projects from our Open Source Project Royalty Scheme – every book that gets sold directly benefits the project.

We have published a lot of titles on Drupal – version 4, version 5, version 6 and now into version 7. Customers appreciate our books, and I like to think the Drupal project appreciates our support with the royalties and information available to feed the demand from a growing community of users.

We are not perfect, but we are trying to support Open Source in a big way, and your comments about us feel rather unfair. I understand that this is simply your opinion, but the facts of our commitment to Open Source cannot be doubted.

davideads’s picture

I'm happy that Packt supports open source projects through its "Open Source Project Royalty Scheme" (seems like a terrible name, but I guess I'm not a marketer) but the financial support seems somewhat besides the point.

What has Packt done to make that money? The Drupal-related titles I've seen, like Drupal 6 Performance Tips and Drupal 6 Attachment Views, are poorly edited and contain incorrect, inadequate, and misleading information. These titles are then heavily promoted on sites like Slashdot and Drupal.org.

This isn't Packt's fault, exactly -- Packt aggressively markets their books. I think it is obviously opportunitistic and shameless, but it makes sense that publishers should promote their titles so they can stay in business. But the book should probably have undergone some technical review before being posted to the Drupal.org home page, which amounts to a ton of free advertising for a book about software that hasn't even yet been released.

thinkyhead’s picture

If Packt is short on really good detail-oriented (and eminently affordable) editors, I know it's a job I'd love to do - proofreading Drupal and other books on subjects close to my heart and work. Maybe you and I should submit our resumés.

tokkie’s picture

About 6 months ago I bought 'Zen Cart', a step-by-step developers guide from packt publishing. The book was very poor, with some technical mistakes, and really lacked solid content. Will not buy another book from this publisher ...

arnolf’s picture

What is this arrogant point of view, me and my team have been developing for years, and recently decided to make a partial move towards Drupal, and a logical point to start is to read a Packt release that concentrates most of the aspects of the workflow, and naturally we will do things our way and eventually contribute as we go alone with it.
Obviously, Drupal.org is the final place to go, but first you have to know what are you looking for, and those books are a good place to start getting comfortable with the terminology and basic best practices and structure.
The theory that "you have to be part of something to write about it" is a complete non-sense, if that was the case, only a small percent of publications would exist, probably self biographies or so.( Shakespeare wasn't a lawyer, [?Bacon?] )
If something claims to be a "Community", don't forget where the term comes from, and "common" is the opposite to "Elite", so start not being a noob in real life and look wider.

juan_g’s picture

>The book is written for Drupal 7 beginners or newcomers to Drupal

That's good, an introductory book helps opening Drupal to more open source users. Drupal 7 beta is coming really soon.

agamesua’s picture

This is a good sign, Drupal every day becoming more popular.
Thanks for the book.

whudson’s picture

While there is an extremely generous discount for the book + e-book bundle, the advertised 20% discount code (Drupal7book20) does not work.

Juliancpackt’s picture

Hi whudson,

Please ensure you're logged in when you apply the 'Drupal7book20' discount.


Dr.Katte’s picture

An author of a book makes an announcement on a site regarding the release of a new book, offering 20% promotional discount. Somebody submits a ticket complaining that the 20%discount code does not work (http://drupal.org/node/910068#comment-3473940). An employee of Packt chips in with a support (http://drupal.org/node/910068#comment-3473948), asking the person complained to login in order to use the discount. Is this (drupal.org) a marketing and ticket support system site for Packt?

Wolfflow’s picture

+1 LOL, what else?

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

jcnventura’s picture

Yes, whudson should not have used d.o to complain about it, but since he did use it, would you have preferred:

"Please submit a ticket for your problem in bugs.packtpub.com, where we will be happy to address this question in a proper forum"

João Ventura

abautu’s picture

I think you should appreciate the fact that a Packt employee took the time answer a question on another site. Other publishers do not reply even on their own sites. His reply (and the money that Packt gave this and other OO projects) means a close relation between them and the Drupal community.

If MerlinOfChaos is so upset for not being involved, he will create some outstanding new features for D7 Panels so that this book will be trashed in the media :P. If Sam was right, then there's no problem.

Sidenote: I got the D6 version of the book as a gift and I was very happy with it. If this book promotes Drupal 7 as well as that book did, then it's

afriend’s picture

Eventually this shows the popularity of Drupal.

jumpbug’s picture


It made good sense to reply to this topic with the solution, since this is where the promotional code was announced.

I have the same problem, came to look for a solution here... and I found it.

Way to go, Packt.

NonProfit’s picture

EDIT: Once I take the time to actually read the comments which have already been posted, I now see that Earl and Wolfflow have previously addressed this...sorry.

I wonder about the wisdom of releasing a book which documents an Alpha release. How can a reference hope to be relevant when code is still in flux (26 critical issues at this writing)?


yautja_cetanu’s picture

Is it likely that these 27 critical issues are going to change the contents of this book that dramatically? It seems like the cool thing about the code freeze and the lack of api changes is that when Drupal 7 is release it is almost completely released (No having to wait for everything else to catch up before it can be used). One thing that is holding me back from Drupal7 is the fact I love books and its going to take ages for these books to come out.

To be honest Drupal is in such constant flux anyway that any point you write a book it will get out of date because most drupal books for users will reference contrib. So usingdrupal has a few things out of date that are confusing despite it being by lullabots.

Wolfflow’s picture


NoProblem at all, your additional comment just underline the big mistake the Authors of the Book and the Publisher in rushing to made public something that will be useless in a very short-time span. I like Drupal and I my self have acquired some Books about:

O'REILLY "Using Drupal" by Angela Byron, Addisson Berry, Nathan Haug, Jeff Eaton, James Walker and Jeff Robbins - A great Work!

and also to make an additional example: APRESS's Pro Drupal Development by John K. VanDyk and Matt Westgate, but in this particular case I had a bad experience because the Book was shortly reviewed as to be update with D6 development and a new version of "Pro Drupal Development" was published. So you can imagine that for getting the best addressing in learning Drupal 6 I had to acquire also the new release, what a pitty. But Readers should find out for them-selves what does mean to buy a Book about Drupal7 before it is stable and complete.

@yautja_cetanu - Oh Yes, (25 Critical Issue) like are now in the moment I comment, can really change a lot ;-)

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

mjohnq3’s picture

This just appeared on Drupal Planet - http://blamcast.net/articles/top-10-drupal-7-books. Looks like Packt isn't the only one publishing Drupal 7 books. Check out the names of some of the authors.

juan_g’s picture

Thanks to John Forsythe and Mjohnq3. I've just updated the list.

New Drupal 7 books, listed chronologically by past or expected publish date (paper editions):

  1. Beginning Drupal 7 (June 7, 2010)
  2. Drupal 7 (September 7, 2010)
  3. Drupal 7 Module Development (print edition: October, 2010; raw ebook available now)
  4. Foundation Drupal 7 (October 25, 2010)
  5. Pro Drupal 7 Development (October 29, 2010)
  6. Drupal 7 First Look (print edition: November, 2010; raw ebook available now)
  7. Drupal 7 - Visual QuickStart Guide (December 4, 2010)
  8. The Definitive Guide to Drupal 7 (January 28, 2011)
  9. Pro Drupal 7 for Windows Developers (January 31, 2011)
  10. Drupal 7 Bible (February 8, 2011)
  11. Going Global with Drupal 7: Creating Sustainable, Multilingual Web Sites (February 10, 2011)
  12. Building Drupal 7 Community Sites (unknown date)

Also, I've read on Twitter they are updating the well-known book Using Drupal.

We are now at just 3 beta blocker issues distance from Drupal 7 beta, when the upgrade path will work and when it seems quite a lot of people is planning to start building sites with Drupal 7, even if it's not officially recommended. And even before, 20,000 Drupal Gardens sites have been created already on Drupal 7 alpha.

It's advisable to wait at least until beta, unless you have a team of Drupal experts like in the case of Acquia's Drupal Gardens. Anyway, the beta release is a matter of days, probably end of September or beginning of October.

stefanwray’s picture

What percentage of book publishers contribute back to code?

Stefan Wray

juan_g’s picture

> What percentage of book publishers contribute back to code?

There are many ways to contribute to open source projects such as Drupal, like for example code, themes, documentation, support, books, etc. About code, see the already linked article by John Forsythe, "Top 10 Drupal 7 Books", and also drupal.org's section Books about Drupal. Among the book authors, we can find a good number of module and core developers.

Naturally, most writers have another job, such as engineers, etc., because of the small royalty they earn, usually 7-10% of the book price.

JohnForsythe’s picture

Thanks for the link :) I was surprised at the number of books, and it turns out I even missed a few.

webchick’s picture

I see people getting pretty upset here, so just wanted to point out a couple of things, as a fellow book author:

#1: Dries and I declared a code freeze for Drupal 7 in Sept. 2009. It was reasonable to make an assumption back then that Drupal 7 would actually be out by Sept. 2010. Unfortunately, that's not what happened (though we're working on it!).

#2: When you sign a contract with a publisher, part of it is a schedule when it will be done (generally broken up like "2 chapters by date X, half the chapters by date Y, and all of the chapters by date Z"). That Z date can sometimes slip a little, but not much. It starts to affect revenue projections of the publishing, if books don't come out within a few weeks of when you promised you'd get it done when you signed the contract.

#3: In a situation like this, when the technology is lagging behind and the book publish date is looming closer, the author and the publisher need to come to agreement about what to do. One option is to indefinitely postpone the title. A couple of consequences happen, though. If the author took an "advance" (meaning, a lump some of money as a stipend to help bootstrap the book that then goes against the sales of the books once it comes out), they now have to pay that money back. That's probably not an option a year or so after it's been spent. The publisher also has to scramble to somehow find another title to slot into its Q3 2010 revenues, etc.

So often, they'll decide to go ahead with the schedule anyway. They do this by culling material that's too unstable (this is how the Organic Groups chapter got scrapped from Using Drupal), and/or release the book with ample caveats around parts that are not fully baked. The idea being that the *majority* of content will still be valuable (and truthfully, not much has changed in terms of the fundamental mechanics of D7 in at least 3 months), and there will always be an errata section and the opportunity for a second printing to fix problems.

#4: Packt Publishing actually does quite a lot for the Drupal project, and open source in general. For starters, they publish a ton of books about Drupal and other open source technologies, which gets this into peoples' faces in real, actual bookstores, increases visibility, and increases the perceived value of these projects. That's huge. They also donate a portion of their proceeds of all Drupal book sales to the Drupal Association, which goes directly to fund Drupalcons, Drupal.org infrastructure improvements, etc. And finally, they hold the annual Open Source Awards, which has over the years netted the Drupal community several thousands of dollars toward various initiatives. So some respect here would be greatly appreciated.

JohnForsythe’s picture

Well said.

ambientdrup’s picture

Well said webchick, and completely in agreement here especially with point #4.

Thanks for posting this.

venkat-rk’s picture

Well said. Frankly, I can't understand the animosity and lack of appreciation for Packt here. Yes, they are a business, but they have also been fair and helpful to many open source projects.

davepoon’s picture

Totally agree with your points.

mermentau’s picture

I really think that since it's featured on the Drupal site that it should have a word of caution for it's target office. That would apply to any book promoted about a Drupal version that's Alpha. The article says that the book is for:

The book is written for Drupal 7 beginners or newcomers to Drupal in general and will help help anyone to create and operate any type of website quickly and efficiently.

I bought a similar book this summer entitled "Beginning Drupal" by Redding and the errors in the book have grown as the summer progressed. I understand the pressures on the authors and publishers. Just let the newcomers know what they are in for.

I am glad I got the book and have learned a ton, but I didn't expect so many errors because I was new to Drupal and didn't realize how the evolution process worked. We have good warnings like "Don't hack the core" and "don't use an alpha on a production site".

Most new people would see a book featured here and not believe that so much could change by the time they read it. When you buy a book you assume for the most part that the text is correct and a mistake there is the worst kind of time consuming bum steer.

mindtrades’s picture


sidharth_k’s picture

@webchick: Agree with your comments.

People just seem to be so pissed off with Packt on this thread. I just can't understand why. I've read a ton of their books and I think they do a good job. I don't think they have done anything wrong to release their Drupal 7 book at this stage.

davideads’s picture

We can argue about the quality of Packt's books til we're blue in the face. The real issue here is that Packt gets a LOT of free advertising on Drupal.org, and that's a huge conflict of interest, generally unseemly, and clearly bothers a lot of people, especially those who find the quality of many of their titles to be fairly poor,. When a publisher is hyping a book about software that isn't even released, it seems even a little ickier and more opportunitistic.

Personally, I'm not really sure who I can ask or how I can ask to see better editorial control over what appears on the Drupal.org front page. But it seems to me the real solution is: Let Packt publish their books as they wish, but stop giving them free advertising on the Drupal.org front page -- a policy that should extend to all commerical publishers, even the ones with GOOD books.

Wolfflow’s picture


Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

davideads’s picture

How DOES one raise this concern? And how does the Drupal.org story approval system work? I'll do some research.

silverwing’s picture

Front page promotion discussions happen in the Webmaster Queue http://drupal.org/project/issues/webmasters?text=&status=Open&priorities...

There's also info here http://drupal.org/front-page-schedule


davideads’s picture

Much appreciated. I should have tagged that #lazyweb.

meichr’s picture

Thanks, webchick, for explaining the process from an insider's view. There is so much efforts to be put into a book, I think this earns to be apreachiated as many fellow commenters have now expressed too.

As one who has bought and read several Drupal 5&6 books from Packt, Apress, O'Reilly, etc. I had a lot of help in getting started with Drupal core and many modules, even if there are "usually" a few mistakes in every book ;-). So I feel well with paying my share for helping me improving my skills with Drupal when also I get something for creating websites with Drupal. ;-) It really feels good, if you can and do so!

Of course, I also appreachiate that there are skilled people working hard on drupal core, modules and basic documentation and provide it all for free. Payment here comes in form of our own contribution of time and efforts according to our own abilities and knowledge into improving what is there. I'm still working out, what my little contributions can and will be ;-). Nothing really comes without payment.

I appreachiate, that Packt is contributing a percentage back to the community, paying respect to the Open Source idea not done by other publishers and companies. This might be an example, giving other publishers the idea to also start giving contriutions to open source projects. I just don't know those which do already.

And to MerlinOfChaos' comment in the beginning of this thread: hopefully such discussions inspire and encourage future book authors to contact the authors of core and and contrib modules to create an even better book. It will automatically pay by improved reviews, sales and most of all: the increase in the author's reputation.
I assume, that Packt will point this out to their future authors, having learnt through these (painful) comments (with a point). Thanks to them for listening.

Btw: I'm also eagerly awaiting MerlinOfChaos' book about Cck, Views and Panels (even if it should concentrate on Drupal 6 versions in the first edition). I think the book has the capability to provide quality knowledge about those modules as previously seen with top quality books like "Pro Drupal Development" for developers and "Using Drupal" for beginners amongst others, due to its author(s). :-)

Enough of my thoughts,

juan_g’s picture

About this book, Drupal 7 by David Mercer, there is a free sample chapter (PDF format). I think it's good to read at least part of it, before giving opinions about an unread book.

They say "the book is written for Drupal 7 beginners or newcomers to Drupal", and indeed it's not an advanced book for programmers like Pro Drupal Development, or an intermediate level book for webmasters like Using Drupal (books for D6 that are going to have D7 versions). Drupal 7 looks to me like a clear and friendly read for those starting out with Drupal. I think this book, like others, is going to be a positive contribution for the current growth of this open source project, so that everyone benefits.

On the other hand, Earl Miles (merlinofchaos), one of the most valuable Drupal developers -Views, Panels, CTools...- made a good point about the need for more communication between book writers and developers. It's true that this cooperation would be very positive as well.

kwpang’s picture

I have been reading this site for quite sometime now ever since i heard about it, over the years i struggle to get some one to design a website which suite my needs with the following requirement :

1)A website which includes : gallery, articles, information pages.
2)within the gallery, it must be able to have different category of accessibility, such is it's open for all viewer or limited to certain viewer with password or email invitation, and within every gallery they also have different accessibility to download the file, such as user group can download full size, group B limited to mid size and so on.. such as the one i have at http://www.kwpang.com and http://www.momentsphotography.biz

But they don't offer article and about page, the limitation only to gallery

I just like to know if Drupal good for this?

juan_g’s picture

> I just like to know if Drupal good for this?

Drupal is an advanced system and can do almost everything related to web sites, by installing suitable modules (there are literally thousands of them) or, sometimes, coding custom modules for very special needs.

A good place to ask details about those topics is:

Drupal Forums -> Before you start

adrianmak’s picture

Any updates to published books like an errata section, will it update to the ebook version for those people have bought the ebook version? Then people can re-download the ebook version.

aamin’s picture

Packt publishing books are good and I really liked David Mercer's earlier book. I think the criticism is uncalled for and we should encourage authors/publishers to come out with more books to increase the popularity of Drupal.

jillbrown’s picture

Foundation Drupal 7 is by far the best book availble (at least in my opinion). Anyone else have a good list to share?


meichr’s picture

I'll give it a look, when it gets published. How did you get a copy? ;-)