Drupal empowers site builders and editors to configure their sites in settings forms. Configuration management lets developers push changes up to live sites to be imported. But developers have to be considerate to ensure imports will not wipe out those changes made directly through the live sites' settings forms. At the least, they have to export the changes before making further tweaks. But admins may make further changes in the meantime too, so developers can...
We've heard of test-driven development, behaviour-driven development, feature-driven development and someone has probably invented buzzword-driven development by now. Here's my own new buzzword phrase: review-driven development. At ComputerMinds, we aim to put our work through peer reviews to ensure quality and to share knowledge around the team. Chris has recently written about why and how we review our work. We took some time on our last team 'CMDay' to discuss how we could make doing peer reviews better. Here's some of our thoughts. Many of them are essentially answers to this question: Why is reviewing hard? How can we make it easier?
Have you ever wanted to create a 'queue' of content that would be published at a regular interval? I have. It seems like this should be one of those things that should be nice and easy to do with Drupal: Set up a nodequeue, schedule some kind of rule to pop the first item off the front of the queue and publish it. But try as I might there just didn't seem to be any...