|
|
[[_TOC_]]
|
|
|
|
|
|
This page is intended to weigh the pros/cons between WordPress and Drupal 8. Everyone has their own preferences, however please consider [our overhaul objectives when assessing the two platforms](https://lab.civicrm.org/marketing/civicrm-website/wikis/home#functional-objectives) and not merely base input on a specific CMS preference.
|
|
|
|
|
|
# Drupal8
|
|
|
|
|
|
* Cost evaluation: marketing/civicrm-website#130
|
|
|
|
|
|
Pros:
|
|
|
|
|
|
* Easier upgrade path than completely changing the CMS (content migration, images/assets, user accounts).
|
|
|
* Compared to d7, provides a more robust content editing (but not as good as WordPress)
|
|
|
* We rely on Views for many types of listings linked to CiviCRM.
|
|
|
|
|
|
Cons:
|
|
|
|
|
|
* Drupal 10 will probably be another big upgrade. Should we bite the bullet and switch to a CMS that provides easier upgrades?
|
|
|
* Drupal is not as popular as it used to be (the same could probably be said of WP, except that WP is more popular, but same growth rate).
|
|
|
* Any improvements made will support Drupal 8 functionality parity with Drupal 7.
|
|
|
|
|
|
# WordPress
|
|
|
|
|
|
* Cost evaluation: TODO
|
|
|
|
|
|
Pros:
|
|
|
|
|
|
* Larger community, more options for page layouts, easier to use, built-in Gutemberg support.
|
|
|
* Lower upgrade costs.
|
|
|
* Any improvements made will support Wordpress functionality parity with Drupal 7.
|
|
|
|
|
|
Cons:
|
|
|
|
|
|
* We will need WP developers to help porting over our custom code.
|
|
|
* No 'Views' integration with CiviCRM. They are not that many, but it is probably the biggest argument against WordPress.
|
|
|
* Content migration path will require much more work. There aren't many tools available, or they must be evaluated/tested. |
|
|
\ No newline at end of file |