With the recipes in this book, you can take full advantage of the vast collection of community-contributed modules that make the Drupal web framework useful and unique. You'll get the information you need about how to combine modules in interesting ways (with a minimum of code-wrangling) to develop a variety of community-driven websites. Each chapter describes a case study and outlines specific requirements for one of several projects included in the book -- a wiki, publishing workflow site, photo gallery, product review site, online store, user group site, and more. With Using Drupal, you will:
Get an overview of Drupal concepts and key modules introduced in each chapter, with a bird's-eye view of each module's specialty and how it works
Explore various solutions within Drupal that meet the requirements for the project, with details about which modules are selected and why
Learn how to configure modules, with step-by-step recipes for building the precise functionality the project requires
Get information on additional modules that will make the project even more powerful
Be able to access the modules used in the chapter, along with other resources
Newcomers will find a thorough introduction to the framework, while experienced Drupal developers will learn best practices for building powerful websites. With Using Drupal, you'll find concrete and creative solutions for developing the exact community website you have in mind.
Using Drupal cuts out a lot of the research time and helps you dive headfirst into Drupal. It does an excellent job of explaining how to rapidly assemble a wide variety of websites using some of Drupal's most commonly used modules. Whether you're new to building websites or an experienced programmer, this book is full of useful information. By the end of Using Drupal, you'll be much more prepared to build the Drupal site you've always wanted.
Is That Site Running Drupal? By Angela Byron
Various attempts at "fingerprinting" a Drupal site have been tried in the past, none of which are completely foolproof. These range from *super* easy stuff like checking for CHANGELOG.txt to checking the source for a reference to "drupal.css" (Drupal 4.7) to checking for common paths like taxonomy/term/1, and /user, (which might be aliased to something else with something like Pathauto/Path Redirect module), and so on. However, since Drupal 4.6, there's a super geeky trick you can use to fingerprint a Drupal site that works 90% of the time.
1. Get Firefox.
2. Get the Live HTTP Headers extension.
3. After restarting Firefox, click Tools > Live HTTP Headers. This'll pop up a little window to the side.
4. Visit a website you suspect of being Drupalish.
5. Highlight the Live HTTP headers window and type "exp", looking for the following in the output: "Expires: Sun, 19 Nov 1978 05:00:00 GMT"
"Classic" Web Problems, Solved Drupal version: 6.x By Jeff Eaton
A lot of energy in the Drupal world goes towards solving complex problems: giving administrators ways to build publishing workflows without writing code, integrating with cool new APIs, automatically translating site content into Klingon... You know. The usual. With all of that energy focused on complex architectural problems, it's easy to lose sight of the simple solutions that Drupal provides for really common "classic" web problems. This really hit home the other week as I sifted through an old Zip disk with archives of sites I'd built for clients in the heady days of the late 90s. One by one, I started ticking off requests my clients had made that today's site-builders can solve in minutes with Drupal modules--no wacky configuration, no complicated recipes. Just a simple, "Yes!" when a client says, "Can you...?"
"...Make a splash page for the site?" No problem. Drop in the Splash module, and you can use any page on your site as an interstitial splash page. It's also smart enough to tie into contextual information Drupal provides--only showing the splash screen to anonymous users, creating section-specific splash pages, and more.
"...Let visitors print out copies of the pages?" While any web browser can print a simple copy of the current page, and custom style sheets can help clean up color schemes and images to make a page look printer-friendly, sometimes, things need tweaking. For example, embedded web links will look like simple underlined text if you rely on style sheet tweaks. Drupal's Print module generates printer-friendly versions of any page, including the creation of URL footnotes at the bottom of each printout. It can also generate downloadable PDFs of any page, and send-this-article-to-a-friend email links.
"...Show visitors a Terms Of Service page before they sign up to post on the site?" Letting users sign up to post comments, subscribe to newsletters, and so on was just catching on when I handcrafted those old-school sites in the '90s. The Terms of Use module handles one of the tricky parts: requiring users to explicitly agree to terms of service before they can create an account. It lets you maintain your terms as a dedicated page on the site that users can read, and present it to them with an 'Approval' checkbox when they create an account.
"...Add a chat page where users can talk in real-time?" Setting up chat rooms on web pages was always a pain in the old days. Even today it can be tricky, and there are quite a few different ways to do it. Flash, AJAX, Java applets, and more are all ready. The Mibbit module for Drupal lets site visitors chat on a custom IRC channel using a simple AJAX interface. Since it uses IRC as its backend, it can point to custom private discussion channels, or public ones like #drupal on the freenode IRC network.
"...Keep other sites from stealing my content using Frames?" This one went out of style for a while, but when Google's AdSense and other advertising networks up momentum, some enterprising individuals resurrected the concept of "wrapping" other sites in HTML frames, presenting ads in the sidebars while leeching the original site's bandwidth and content. JavaScript can help: script snippets can force your page to open in a dedicated window instead of a frame, and the FramePrevention module makes that trick automatic. None of these modules are crazy, groundbreaking tools that get their own articles and tutorial videos. Like many of the tools in the Drupal world, though, they do the heavy lifting that lets us focus on the really complicated tasks. Looking back, it's hard not to sigh and wonder how much time could've been saved if I'd had them at my disposal in The Olden Days...
About the Author
Angela Byron is an open source evangelist, and has been called a Drupal freak by those in the know. She got her start as a Google Summer of Code student in 2005 and since then, she has immersed herself in the Drupal community. Her work includes coding and reviewing patches, creating and contributing to modules and themes, testing and quality assurance efforts within the project, improving documentation, and providing user support on forums and IRC. Angela is on the Board of Directors for the Drupal Association, and helps drive community growth by leading initiatives to help get new contributors involved. She is a sought-after lecturer on many themes, especially the topic of women in Open Source.
Addison Berry is deeply involved with Drupal and takes part in many aspects of both the software and the community. She contributes patches to core Drupal, maintains several contributed modules, and is active in various mentoring programs such as the Drupal Dojo group and Google's Highly Open Participation (GHOP) program. Addison helps maintain the drupal.org website, and is a permanent member of the Drupal Association General Assembly. Her work focuses on improving Drupal documentation and she has worked to provide a wide range of tutorials covering all aspects of Drupal from community involvement to code.
Nathan Haug is one of the forefront user-interface developers in the Drupal project. His interest in combining design and software implementation led him to complete undergraduate degrees in both Visual Communications and Computer Science. Using these skills he developed significant UI improvements for the Drupal 6 release, including Drupal's drag-and-drop implementation and a framework for easy AJAX-like behaviors. Nathan is considered the leading JavaScript developer in the Drupal project. In 2007, he led a development team at SonyBMG to build a Drupal-based platform for community websites around each of SonyBMG's music artists. He spends much of his time working between popular contribute modules such as Fivestar and Webform, or working to improve functionality in Drupal core.
Jeff Eaton has been building software for the Internet and desktop applications for over a decade. He's participated in projects ranging from web-portals for communities and nonprofits, to enterprise client-server applications for retail industries, to large-scale web applications for companies like Dow AgroSciences and the Chicago Board of Trade. In 2005, he began developing solutions based on the open-source Drupal content management framework. In the years since, he's become a core developer for the Drupal project, specializing in architecture and API development. In his capacity as a consultant for Lullabot Consulting, LLC, he's helped plan and build the software infrastructure for Drupal sites including MTVUK's music portal, SonyBMG's artist site platform, and Fast Company's groundbreaking business networking site.
Passionate about both technology and teaching, James Walker is Lullabot's Director of Education where he oversees the company's public workshops, seminars and private Drupal trainings. A leader in the Drupal community, James is a founding member of the non-profit Drupal Association and the Drupal security team. As a long time member of the Drupal community, James maintains over a dozen modules and has contributed countless patches to Drupal core. A long time believer in Open Source and Open Standards, James has spent years co-ordinating Drupal's involvement with other communities such as Jabber/XMPP and, most recently, OpenID. An engaging speaker, James is a frequently requested presenter at many types of technical conferences. His humorous and informative lectures have been among the most well-attended at DrupalCons, starting with the first - four years ago.
Jeff Robbins is co-founder and CEO of Lullabot. He worked at O'Reilly & Associates as an illustrator and systems administrator as the world wide web came into being. He was involved in the early stages of the first commercial website, O'Reilly's Global Network Navigator, but left to start one of the first web design companies, Liquid Media, in 1993. Considered by many to be the voice of Drupal, Jeff hosts Lullabot's weekly Drupal podcast, the #1 Drupal podcast in the world. Additionally, he has contributed over 20 Drupal modules and themes.
This book has been eagerly awaited as the first O'Reilly volume covering Drupal, and having been written by such a rockstar team of Drupal pros.
It's also the first book to focus on a wide range of third party contributed modules rather than just Drupal core, or a narrow subject area of modules. It's written for Drupal 6, although the book would be fairly applicable to Drupal 5 (with the caveat that one of the major modules, Views, is completely different for Drupal 6 - the underlying concepts are similar though).
The first thing that struck me about this book is its fundamentally different approach from most early Drupal books, as well as the kinds of books you find in the early stages of any new technology's mainstream acceptance. It's not simply a higher quality rehashing of handbook pages and technical how-tos, but it has an incredibly cohesive and clever process through the entire book.
Every main chapter of the book will: * Introduce an example scenario that's easy to relate to. For example, an early chapter that covers creating a simple site for a Mom & Pop shop has this sample case study: "in order to update the web page content each week, they currently pay their next-door neighbor Goldie to hand-edit the page" * Outline what you're going to be building * Explain why certain decisions or trade-offs were made when creating this site, and highlight alternative choices depending on your particular situation * Explains step-by-step how to complete the site with lots of tables and screenshots, pointing out gotchas and important concepts along the way * Ends with a "Taking It Further" section with suggestions for other features or future modules to watch that are related to the site recipe
The hands-on approach of this book takes you through a single, cohesive example in each chapter. This gets you building a site to completion at every step. This approach reminds me of the different ways to learn a musical instrument such as piano or guitar - you can start with theory and technique and practice your scales first, or you can just learn some chords and be able to whip out a few simple pop songs your first afternoon. This book is the chords.
It also has some great moments of explaining fuzzy concepts that are difficult to understand without significant Drupal experience. The Using Drupal team shows their years of expertise training users and implementing Drupal sites in gems such as this, describing whether you should use taxonomy or a CCK field for content categorization: A general rule of thumb is that if you can remove the field and the content type still makes sense, use Taxonomy. An article filed under a "Technology" category is still an article if you remove the category association, so Taxonomy is a good fit. If the field is part of a piece of content, such as an album's recording artist, then CCK is generally a better choice.
Using Drupal will take you through building a:
* Simple website with blog for a mom & pop grocery store, including a WYSIWYG editor and uploading images to content * Job posting board for a university, which introduces the key CCK and Views modules * Product reviews site with user ratings, Amazon product data importing, some simple CSS tweaks using the CSS Injector module, and more CCK/Views * Wiki, which brings in revisions, input formats, and Pathauto module * Local arts news site, which takes you into Actions, Triggers, Workspace, Workflow (both as a concept and module), and Views Bulk Operations to create an administration page * Photo gallery, with ImageField, ImageCache, much more Views and some site display tweaks * Multilingual website with a strong overview of concepts, then Locale, i18n, and the Localization Client * Event management site with calendar and attendees * Online store using Ubercart (focuses on basic store setup, products, attributes, and orders - you'll still need to set up payment methods)
It also covers a few additional topics:
* An overview of Drupal, and where to get help * Basic theming (this is the only time you'll see code!) * Installing and upgrading Drupal and modules * How to choose modules and participate in the community
So what's it missing?
Obviously Using Drupal only scratches the surface of the many, many types of sites you can build with Drupal. There are a few major topics you won't find covered in here - membership sites with protected user access, Organic Groups (a chapter that didn't quite make it due to module readiness for D6), more advanced magazine/newspaper-style sites with modules like Node Queue and Panels, multimedia (there's another book for that!), or social networking sites. However, I think they picked a great selection of site recipes to cover in a relatively small amount of space, and each recipe will get you a solid site built.
The book will also direct you to two additional resources available online: the finished demo site for each chapter for you to browse, and a download package containing installation profiles with the same versions of modules and themes used on each site. The installation profiles will set you up with a clean slate with your modules all prepared for you to start following along step-by-step in each chapter.
Other things I really love about this book:
* It isn't afraid to recommend helpful modules early, such as Administration Menu * It highlights common newbie gotchas, such as using the blog module when you really want a story * It points out future modules or alternatives to watch, for example, the WYSIWYG API * It gives contrib modules such as CCK and Views the foregrounding they deserve when learning Drupal
This is the book I wish I had when learning Drupal. We're even giving away copies of it at [...] because we love it so much. I would recommend it wholeheartedly to anyone new to Drupal, intermediate users who want to take their skills to the next level or brush up on Drupal 6/Views 2, or anyone who actually needs to build a site similar to the recipes listed above. And, y'know, anyone else who's ever built or wanted to build a website :)
I'm just learning Drupal and this book has been invaluable. Via a "case study" approach, Using Drupal shows you many well-trodden paths through the Drupal forest using off-the-shelf modules to build out 9 sites.
As a Drupal newcomer comfortable writing code (like me), your first instinct will probably be to start adding PHP to your theme, your blocks, etc. to do what you want. Using Drupal shows you how other developers have solved many common problems/features and packaged up the solutions as modules. It's like being able to start out on your first solo project after being on a team that has already completed 9 Drupal projects. You'll already have a set of "tried and true" design patterns to leverage and know how Drupal sites tend to be built.
Using Drupal can only cover a handful of the numerous Drupal modules out there, but it saves you time by pointing out some of the most useful and commonly-used modules and showing you how to use them in practical situations.
This book is not a comprehensive introduction to the basics (how to install Drupal, basic configuration, etc.), but once you have the basics and want to start "Using Drupal" on real projects, this should be your next read.
This is one of many books coming out that focuses on the very confusing contributed modules aspect of Drupal. There are so many and it's hard to know what's available, and what choices to make. The book has a focus on some of the most popular ones, like CCK and Views, but covers many others as well. I particularly like that it often compares the options available for doing a specific thing and explains why they chose the one they did, and why you might choose another one.
I gave the book four stars instead of five because the printed edition needed some serious proofing. If you get the printed edition, be sure to go to the website where you can find errata (corrections). It was very confusing and time-consuming to figure out that figures were out of sync with the figure references in the text in some cases. There were also some typos that make some instructions technically wrong. But given how much people wanted to get this book, maybe they rushed it.
