... | ... | @@ -7,14 +7,16 @@ This page is intended to weigh the pros/cons between WordPress and Drupal 8. Eve |
|
|
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)
|
|
|
* Provides a more robust content editing experience than Drupal 7, and support for Gutenberg is complete or near completion.
|
|
|
* We rely on Views for many types of listings linked to CiviCRM.
|
|
|
* Immediate costs to migrate appear to be relatively low.
|
|
|
|
|
|
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.
|
|
|
* Long term maintenance costs are significant.
|
|
|
|
|
|
# WordPress
|
|
|
|
... | ... | @@ -22,12 +24,12 @@ Cons: |
|
|
|
|
|
Pros:
|
|
|
|
|
|
* Larger community, more options for page layouts, easier to use, built-in Gutemberg support.
|
|
|
* Lower upgrade costs.
|
|
|
* Larger community, more options for page layouts, easier to use, built-in Gutenberg support.
|
|
|
* Lower ongoing upgrade costs and lower longer term maintenance 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 |
|
|
* No 'Views' integration with CiviCRM. There 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/purchased. |
|
|
\ No newline at end of file |