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:
"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?"
"...Let visitors print out copies of the pages?"
"...Show visitors a Terms Of Service page before they sign up to post on the site?"
"...Add a chat page where users can talk in real-time?"
"...Keep other sites from stealing my content using Frames?"