A recent project of mine has been ContribKanban.com for the Drupal community. The name speaks for itself - it provides a way for contributors to work on Drupal.org project issues queues through a kanban board. This app has two purposes: visualize the Drupal.org project issue queues in a useful fashion, and provide an experiment that tries to fully utilize Drupal.org APIs.
Yesterday I released a Chrome application to provide a simple method for keeping track of Drupal.org project issues. Take a Drupal.org issue number (the node ID) and add it to the app. It will then utilize Drupal.org's REST APIs and keep track of the issue. This allows you to keep a collection of important issues and periodically check their status.
I've put the Chrome packaged app source up on GitHub: https://github.com/mglaman/drupalorg-issue-tracker
Make the Media: YouTube module responsive friendly with this tidbit of CSS. This snippet provides a responsive solution, but doesn't force it to be full width (it will respect the width set on the elements.)
Drupal Commerce has a very interesting "Add to Cart" form. The add to cart form is a field formatter for the product reference field (or even entityreference field.) In a general sense, a node has a product reference field using the "Add to Cart" formatter. What makes it more unique is that this form exposes certain fields from the product entities, but also the line item type being used. Specific fields on products can be exposed as attributes, things you pick to make your purchase. Exposed line item fields allow you to get customer input values on that specific item added to the cart.
It's been a long time, but I've decided to work out a new version of Facebook Albums. This will bring it up to speed with any Facebook API changes and WordPress. The plugin hasn't had any real work done since 3.5 came out. The main goal is to provide a better class at handling API interaction and hopefully more functionality.