There's a module for WHAT?

Events happening in the community are now at Drupal community events on www.drupal.org.
jsorgen's picture

Being a relative Noob, I'm very interested in Drupal best practices. Attending DDCLA was about the best thing for me.

One thing that kept happening was hearing the presenter saying "There's a module for that!" OK, but I didn't write them all down, and there were so many across the sessions I know I missed most of them. What might seem obvious to some are not so for newbies like myself.

Maybe someone's got a nice list of the modules mentioned during DDCLA? Where? Maybe post here?

Thanks!
Jeff

Comments

For a great survey of useful

rgon's picture

For a great survey of useful modules, listen to this Lullabot podcast

Top 40 Drupal Modules

Top 40 Drupal Modules

pcher1bw's picture

Is there a written list that goes with it, I'm definitely better at reading then listening.

Paul Chernick
CEO
Chernick Consulting
(310) 569-2517

Reading versus listening

pcher1bw's picture

I guess I should check links before I ask dumb questions.

Paul Chernick
CEO
Chernick Consulting
(310) 569-2517

Here's another

Techivist's picture

Here's another list of the top 40 Drupal modules. Acquia did a webinar where Dries listed out the top 40 modules in D7: http://acquia.com/resources/webinars/drupal-7-top-40-core-modules-and-wh...

I would normally suggest the Acquia webinars but I've noticed they've become way too corporate (i.e. geared WAY more to large businesses vs. web developers) & not as information-packed as they used to be so less useful for us webdev types. Still, there's a couple good ones in there.

HTH.

Miguel Hernandez - www.migshouse.com
Founder & CEO - The OpenMindz Group
Writer- Linux Journal & TechZulu

Module overload

rjbrown99's picture

There's a module for just about everything - but you need to be cautious when eating at the module buffet. Each module has the dual potential to add a really cool feature and also bog down your site. If you are only dealing in low traffic sites this probably won't matter, but some consideration should be given in production as to what you really need. Quick rule of thumb: disable any module that you are not explicitly using, and also disable the devel module on a production site.

You can also ask for recommendations here or via IRC - both are likely a good option to help get your arms around modules. Choice of modules is one of the difficult parts of being a new Drupal user.

Go to d.o

stevenator's picture

the best thing to do to start to get familiar is to go to drupal.org and view all of the known contrib modules. Sort by most installed and you'll start to get an idea of what the community considers necessary and also stable. I also agree with all of what @rjbrown99 has said about best practices. Remember that everything is open source contrib under GNU licensing so it is buyer (or freeloader) beware.

Here is the link at d.o

http://drupal.org/project/modules

I find attending meetups

mike stewart's picture

I find attending meetups regularly to network and learn PLUS growing your personal network is often the best way to find what the "good" modules are. plus your own trial and error - and then sharing that with the group.

there's are also "use case" reasons to pick certain modules (panels vs context vs blocks vs templatfile.php.tpl, etc for layout). or sometimes just a matter of taste, such as when choosing and admin related module.

--
mike stewart { twitter: @MediaDoneRight | IRC nick: mike stewart }