Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
2 added 416 characters in body
source | link

The platform while important is just one aspect of the implementation. If you do decide on Drupal (which is what I would recommend given any NPO/NGO with 5 to 10+ FTE) please don't bid the project out to the lowest bidder and then get a WordPress consultant doing a Drupal implementation with CiviCRM (and vice versa, though that's rare). This type of mismatch can cost your organization lots of time and valuable resources in having to re-implement large chunks of the implementation (we've had several rescue projects like these and they are not fun!)

We've also had good experiences for using both simultaneously (i.e. WordPress for the CMS front-end and Drupal+CiviCRM for the CRM back-end), but the overhead is higher in terms of managing themes or changes to the look and feel since now you have to update both the WordPress theme AND the Drupal Theme. Another downside is that the systems are defacto decoupled so it's harder to create more complex workflows.

The platform while important is just one aspect of the implementation. If you do decide on Drupal (which is what I would recommend given any NPO/NGO with 5 to 10+ FTE) please don't bid the project out to the lowest bidder and then get a WordPress consultant doing a Drupal implementation with CiviCRM (and vice versa, though that's rare). This type of mismatch can cost your organization lots of time and valuable resources in having to re-implement large chunks of the implementation (we've had several rescue projects like these and they are not fun!)

The platform while important is just one aspect of the implementation. If you do decide on Drupal (which is what I would recommend given any NPO/NGO with 5 to 10+ FTE) please don't bid the project out to the lowest bidder and then get a WordPress consultant doing a Drupal implementation with CiviCRM (and vice versa, though that's rare). This type of mismatch can cost your organization lots of time and valuable resources in having to re-implement large chunks of the implementation (we've had several rescue projects like these and they are not fun!)

We've also had good experiences for using both simultaneously (i.e. WordPress for the CMS front-end and Drupal+CiviCRM for the CRM back-end), but the overhead is higher in terms of managing themes or changes to the look and feel since now you have to update both the WordPress theme AND the Drupal Theme. Another downside is that the systems are defacto decoupled so it's harder to create more complex workflows.

1
source | link

The platform while important is just one aspect of the implementation. If you do decide on Drupal (which is what I would recommend given any NPO/NGO with 5 to 10+ FTE) please don't bid the project out to the lowest bidder and then get a WordPress consultant doing a Drupal implementation with CiviCRM (and vice versa, though that's rare). This type of mismatch can cost your organization lots of time and valuable resources in having to re-implement large chunks of the implementation (we've had several rescue projects like these and they are not fun!)