Backdrop CMS is essentially Drupal 7 plus a Configuration Management System (and a few hundred other improvements).
Configuration Management exists both in Backdrop CMS and in Drupal 8/9/10, but it is managed a little differently in Backdrop. In Drupal, the active configuration lives in the database, and you only need to worry about managing your staging configuration. In Backdrop, both the active and staging configuration can be managed in version control, allowing for more flexibility, and different options for how to manage these files.
- What is configuration management, and why do we need it?
- Comparing changes in configuration using the Configuration Management Interface
- how to deploy Configuration changes using the Configuration Management Interface
- Comparing changes in configuration using git diff
- how to deploy Configuration changes using git
- Best practices for how to manage configuration simply
- Best practices for how to manage configuration for multiple developers
- Best practices for how to manage configuration for multiple instances of your website (for example: on Pantheon)
- Coning soon: How to use configuration sets, or "Recipes"
- Coming soon: the "Features" module for Backdrop (using Configuration)
Backdrop's Configuration Management System is my favorite improvement because it saves me so much time during maintenance, upgrades, and site builds.