Kristof De Jaeger (swentel on drupal.org) joins Ryan Price and Mike Anello on the latest edition of the DrupalEasy podcast to talk about the (now unanimously agreed-upon) awesome Display Suite module. Other topics discussed include a (in our opinion) slanted Smashing Magazine article, IE9 automatic updates, and Media module + Solr goodness.
- Display Suite, the screencast series, Kristof’s blog: http://realize.be/
- How Wordpress Took the CMS Crown from Drupal and Joomla - Smashing Magazine
- IE9 to offer “Chrome style” automatic updates
- Now search Media Modules for D7 Apache Solr, update-in-place, Views Media Browser and Translation (thx Achieve Internet!)
- Happy Holidays!
Picks of the Week
- Mike - Administration Menu by Daniel Kudwein (sun on drupal.org)
- Ryan - CSS3 selectors simplified by Megan McDermott (DrupalChick on drupal.org)
- Kristof - Panelizer module by Earl Miles (merlinofchaos on drupal.org) Panelizer stock: http://drupal.webstocks.ws/project/panelizer
Site of the Week
Common Sense Media http://www.commonsensemedia.org/ - Reviews of movies, games, apps, & more so parents can make informed
If you'd like your site highlighted, please submit it at http://DrupalEasy.com/siteoftheweek.
Follow us on Twitter
If you'd like to leave us a voicemail, call 321-441-3964. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or German language lessons for Andrew. If you'd rather just send us an email, please use our contact page at http://DrupalEasy.com/contact
Another stellar podcast, gentlemen!
Incidentally, the "CSS3 selectors simplified" link appears to be broken (simply an extra URL at the beginning).
In the part of the podcast concerning the Smashing Magazine article about the three leading CMSs, there was some speculation as to why online searches for "Joomla" outnumbered those for "Drupal" 3-to-1. Based upon my experience talking with other freelancers and their business prospects/clients, I think the main factor is that Joomla is most popular with web site builders who are not hard-core developers -- much more so than Drupal. Consequently, the site builders approach prospects with proposals for building sites using Joomla, prompting the prospects to search for more information on it.
Thanks for the kind words (and the bug report - the link is fixed).
Good point on the marketing aspect of Joomla vs. Drupal...
Another great podcast. Thanks!
I think I finally got a way to put words on the differences between Display suite, Panels and Page manager:
- Display suite is a tool for managing view modes for entities.
- Panels is a tool for creating arbitrary layouts.
- Page manager is a tool for mapping paths against content (or responses), and also for pulling in contextual data.
Examples of how these modules work together
- Display suite is (for example) awesome for creating a special layout for teasers. This could be done using a Panels layout, but Panels cannot in itself affect how teasers are displayed. Display suite can also create new view modes, which the other modules can't.
- Panels is (for example) awesome for creating customized layouts on custom pages or blocks. While Display suite can change the layout of entities, it cannot affect other parts of your Drupal site.
- Page manager is (for example) awesome for adding new tabs on user pages beloning to users with a particular role, or on node pages containing a particular taxonomy term. Or for pulling in data about referenced entities when displaying a node. (None of this can be done with the other modules.)
Examples of how these modules overlap
- Both Display suite and Panels can be used to change the full view mode of entities. Display suite does this by altering the view mode itself, while Panels does this with the panel nodes. If used with Page manager, you can also override the standard entity page, having it display layout and content built with Panels (or possibly some other module).
- Both Dispaly suite and Panels provide Views with new row styles, allowing Views to output its result in customized layouts.
I think that needs to go on a handbook page somewhere!