I wrote a blog post that reflects my own thoughts on how I personally view Backdrop CMS as part of the larger community and a service to those being left behind by Drupal 9+.
I like Drupal 9 in some situations and for some client and still consider myself part of the Drupal community. I wish there were some way for the Drupal community to acknowledge that Backdrop CMS might meet the needs of some Drupal 7 users and that adopting Backdrop CMS is not abandoning Drupal, it's just a small fork in the road.
Backdrop CMS - Providing a Soft Landing for Drupal 7 Sites
I'd love feedback.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface
I'm not sure if this is helpful, but here are pages in Backdrop documentaion about server level permissions. https://docs.backdropcms.org/documentation/file-permissions-and-ownership...
Update Core and Theme via Web interface
Just ran into this issue while upgrading modules on a site I'm setting up. I'm confused. Does this mean that /modules needs to be owned by www-data? (Not just that www-data...
Update Core and Theme via Web interface