Last weekend I gave a talk on "Footless Drupal" about how Drupal 8 is using declarative programming for configuration, how the Config in Code (CINC) module is aiming to backport that to Drupal 7, and how it's already possible to use custom configuration workflows outside the default Drupal interfaces.
This is an update to a previous post I wrote on adding classes to blocks in Drupal 7
"If you're not testing, you're doing it wrong." I can't remember how many times I've heard those words. Each time, I'd feel a little pang of guilt, a little bit of shame that every day, I wrote code for myself and clients that wasn't tested. I'd be frustrated with the developers who repeated that mantra. Sure, it was easy to say, but hard to live up to. How do I test? What do I test? Should I test? How would I justify the costs?
Our client, Human Rights Watch, publishes a large volume of content and with the redevelopment of HRW.org, they wanted a way to curate their content in more meaningful ways. One way we did this was by showing what content is shared most frequently across a variety of social networks.