club) • 2006: My first Drupal site • 2007: First NY Observer Drupal site • 2008-10: Major Drupal adoption in media, higher ed and enterprise: NBCU, Viacom, Zagat, Sony BMG, Economist, UC Berkeley, …
two completely different systems. • No central registry of site URLs. • Most templates expect the context of a “loop” over one or more “posts”, all managed in globals. • Creating new DB tables not kosher; no custom entities except by repurposing posts, users, terms.
point is its editing tools (which, remember, a lot of your editorial folks already know and love) • Its other major selling point is its media management.
2006 (when WP first introduced user roles) • CCK complete household name by D6 • Core in D7 (programmable with Features etc) • Use case = whatever you can think of.
us since D5, and we all know and love it. • In WP, form data has to be passed back and forth with $_POST and $_GET. • In Drupal, validation and sanitization built- in, in WP you’re on your own.
• WordPress is a kids’ toy • WordPress is just for blogging • The backend is built for tiny sites only WordPress folks say… • Drupal is a byzantine nightmare • All the configuration is in the database • The backend is alienating to non-technical folks
form workflows, wide arrays of content types) • Others suggest WP (lots of media management, challenging editorial culture) • Speaking from authority on both platforms can be incredibly powerful for both sales and strategy.