Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
CiviCRM Website
CiviCRM Website
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Marketing
  • CiviCRM WebsiteCiviCRM Website
  • Wiki
  • WordPress vs. Drupal 8 Comparison

Last edited by josh Aug 01, 2019
Page history

WordPress vs. Drupal 8 Comparison

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 and not merely base input on a specific CMS preference. This issue can be used for ongoing discussion

Drupal8

  • Cost evaluation: #130

Pros:

  • Easier upgrade path than completely changing the CMS (content migration, images/assets, user accounts).
  • 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

  • Cost evaluation: TODO

Pros:

  • Larger community, more options for page layouts, extensions, etc.
  • Easier to use from a content perspective, built-in Gutenberg support, several mature page builders.
  • Lower ongoing upgrade costs and lower longer term maintenance costs.
  • Any improvements made will support Wordpress functionality parity with Drupal.

Cons:

  • We will need WP developers to help porting over our custom code.
  • No 'Views' integration with CiviCRM. There are not that many, but it is probably the biggest argument against WordPress.
  • Content migration may be more difficult (though tools do exist that may make this a non-issue)
  • Higher security risk. Will likely need different measures in place.
Clone repository
  • Current Site Core Functions
  • Defining Audiences
  • Experts Listing
  • Peer Sites
  • Split Sites
  • WordPress vs. Drupal 8 Comparison
  • drupal8 content editing
  • Home
  • website tech revamp
  • website translation