| ... | ... | @@ -9,9 +9,9 @@ CiviCRM Standalone aims to make CiviCRM work without a CMS. This was possible so |
|
|
|
- User management options in Standalone were limited, and SSO was recommended.
|
|
|
|
- Most developers came from the Drupal world, and were more comfortable with Drupal tooling.
|
|
|
|
|
|
|
|
As CiviCRM has evolved, so have content management systems, and the organizations using CiviCRM. Notably, we have seen that as organizations upgrade from Drupal7, they are most likely to move away from Drupal, and therefore from CiviCRM as well. What used to help us grow, is now a limiting factor.
|
|
|
|
As CiviCRM has evolved, so have content management systems, and the organizations using CiviCRM. Notably, we have seen that as organizations upgrade from Drupal7, they are moving away from Drupal, and therefore from CiviCRM as well (we do not see a growth in WordPress, for example, and only a small increase in Drupal8/Drupal9 adoption).
|
|
|
|
|
|
|
|
It seems like a good time to bring CiviCRM Standalone back:
|
|
|
|
Regardless of CMS debates, it seems like a good time to bring CiviCRM Standalone back:
|
|
|
|
|
|
|
|
- CiviCRM tooling has improved a lot, from SearchKit, to Form Builder, 'cv', the extension and theming eco-system. Having a CMS is not a requirement anymore.
|
|
|
|
- Managing a website and a CRM coupled together can be challenging
|
| ... | ... | |
