Session Description
Backdrop CMS and Drupal tackle configuration management in surprisingly different ways, despite their shared roots. Backdrop uses JSON, while Drupal uses YAML. Backdrop offers file-based active configuration by default, with the flexibility to store it in the database since version 1.28. Drupal ties configuration to a UUID for site-specific workflows, but perhaps limits portability without extra effort.
As someone who works with both systems—and more than occasionally edits configuration files manually—I’ll share insights into their strengths, challenges, and quirks. We’ll explore the tools and workflows each platform provides, comparing how they handle configuration management and what these differences mean for real-world projects.
Key Takeaways
- Key differences between Backdrop and Drupal configuration management.
- Practical tips for working with configuration in both systems.
- Lessons learned from frequent manual editing of configuration files.
Target Audience
This session is for developers and site builders who work with Drupal, Backdrop, or both.
