Abstract
When building a Drupal site, “there’s a module for that” can be the sweetest words you can hear. Modules are nicely packaged bits of code that extend what Drupal can do. With thousands of contributed modules, the odds are good that someone has written one that does something close to what you need. The main challenge, then, is two-fold:
-
1.
Figuring out exactly what you need.
-
2.
Finding the best module to accomplish that goal.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2011 Benjamin Melançon, Jacine Luisi, Károly Négyesi, Greg Anderson, Bojhan Somers, Stéphane Corlosquet, Stefan Freudenberg, Michelle Lauer, Ed Carlevale, Florian Lorétan, Dani Nordin, Ryan Szrama, Susan Stewart, Jake Strawn, Brian Travis, Dan Hakimzadeh, Amye Scavarda, Albert Albala, Allie Micka, Robert Douglass, Robin Monks, Roy Scholten, Peter Wolanin, Kay VanValkenburgh, Greg Stout, Kasey Qynn Dolin, Mike Gifford, Claudina Sarahe, Sam Boyer, and Forest Mars, with contributions from George Cassie, Mike Ryan, Nathaniel Catchpole, and Dmitri Gaskin
About this chapter
Cite this chapter
Nordin, D., Hakimzadeh, D., Melançon, B. (2011). There’s a Module for That. In: The Definitive Guide to Drupal 7. Apress. https://doi.org/10.1007/978-1-4302-3136-3_4
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3136-3_4
Publisher Name: Apress
Print ISBN: 978-1-4302-3135-6
Online ISBN: 978-1-4302-3136-3
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books