3

Thinking about this topic, I'm wondering about the strategy of CiviCRM in terms of supported CMS?

CiviCRM can now be embedded on 5 CMS (DRUPAL 7, DRUPAL 8, Joomla, WordPress and Backdrop) and this asks a lot of work from the community to maintain functioning versions on all of them, but not only because it also involves specific documentation for each CMS or functional differences between CMS because Webform is not Caldera or Gravity form and I don't know about Joomla. I can think of this heterogeneous environment to be more of a drawback in 5 years.

Even if it's very user-friendly, is this strategy sustainable in the long-term? We already use 2 CMS (DRUPAL 7 and WordPress) and with the end-of-life of Drupal 7 we'll probably switch our Drupal instances - some or all of them - to Backdrop in 2021. Which means a 3rd CMS to learn (same-same but always different) and manage.

Is there a decision taken from the board to stop maintaining in the future Drupal 7 or to make CiviCRM a stand alone web application like vTiger for example, to focus on Drupal 8/9 or to go to another direction?

Who knows about this?

Improve this question
1

It's a good question and it has been asked several times over the years. There are pros and cons for both. Up until around v3.0 civi did have a standalone version, and at the time it was felt that supporting that required too much resources, but as you note there's now 5 CMS's and it seems like just as much work.

This post is old but not much has changed except I don't think CiviDesk still offers their version.

For drupal 7 specifically, when drupal 7 itself becomes unsupported civi will probably drop official support for drupal 7, but the community might still unofficially support it for a little longer the same as drupal 6.

Improve this answer
  • thanks Demerit. Do you know if this point has been discussed and decided in the CiviCRM board? Simply said, is there a clear strategy about the integration of CiviCRM? – Guillaume Sorel Aug 6 '20 at 14:38
  • The only official roadmap I know of is here: civicrm.org/about/roadmap. It doesn't mention anything about this topic. There is sometimes talk in the chat channels about this subject. Otherwise "strategy" comes from either lab tickets, or pull requests that magically appear, but on this topic it's usually because something broke, but indicates that the direction is to keep integrating with CMS's. – Demerit Aug 6 '20 at 14:47
  • thanks again for the link to the roadmap. ok so near term goals in terms of usability and functionality but nothing clearly defined concerning the integration within the CMS. (that said I have no particular point of view about should or should not be done. I'm just trying to define our own strategy. – Guillaume Sorel Aug 6 '20 at 15:57
  • This is a great discussion! I've been using Joomla for many years and have not explored other CMS in several years. With that, I've now been using Civicrm with Joomla for a few of those years. While Joomla is supported here, it does not seem to have the popularity of the others...meaning topics can be far and few between. I am considering a move over to Drupal, especially with better integration between Civicrm and Drupal. What I'm questioning now is if this a smart move for the long-term support. – Taylor Pyles Jan 3 at 18:29
  • If you mean moving to drupal 7 instead of 8/9, then no I don't think that's a good idea for long-term. If you mean moving to drupal 8/9 because integration, meaning e.g. Views and Webform, is important to you, then that will be supported long term. If you aren't really planning to use that type of integration and are worried civi might drop joomla, then no I would stick with joomla since that will still be supported long-term for "integration" such as for login accounts. – Demerit Jan 3 at 18:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.