This has been a long time in the making. It's really exciting to have the work I've been doing recognized, and also have the ability to leverage that work to improve documentation and help build a stronger Docs Team. On top of that, my community spotlight was also posted today, which is incredibly heartwarming.
This past weekend we attended the Pacific Northwest Drupal Summit and I gave an introduction to open data and beautiful maps. I talked about open data, covered the creation of a map in under 10 minutes, and discussed how to create beautiful maps using advanced techniques like custom tilesets. The video is already online thanks to the hard work of Justin Carlson, posted on his blog here and embedded below:
It was an incredibly jam-packed weekend for Drupallers here in the Pacific Northwest, with the 2nd annual PNW Drupal Summit in Vancouver. The Summit is a weekend conference that is targeted towards people already working with Drupal (moderate to advanced level), and is done in a regional mini-DrupalCon style: pre-scheduled sessions/tracks, keynotes from Drupal 7 maintainer Angie Byron (aka. webchick) and Chapter 3's Josh Koenig (aka. joshk), and Drupal 7 code sprints (that resulted in bringing the Drupal 7 criticals count from 13 to 8 over the course of the weekend, HOOAH!)
A few weeks ago, I embarked on my first overseas trip to go to Copenhagen for this year's European DrupalCon. It was my 4th DrupalCon to date, but I've been wanting to attend one of the European ones for a while, as they have a reputation for having a different vibe than the North American ones (and of course so I could finally see some of Europe!)
The Core Dev Summit (+ Code Sprint Day)
Like the last conference in San Francisco, it was prefaced with the Core Developer Summit, which is a full day of presentations, discussions, and code sprinting on the core Drupal platform. The Core Dev Summit is the single day (twice a year at this point), where a good number of the people who work on Drupal core come together to take a step back and discuss in-depth any ideas or concerns. This often leads into some dedicated sprinting on core related issues (as well as some of the most crucial contributed modules).
With Drupal 7 down to 30 critical bugs, and Drupalcon Copenhagen just around the corner, it's only a matter of time before Drupal 7.0 ships. We want to make sure our Drupal 7 documentation is in great shape for this fantastic new release, and the Documentation Team could really use YOUR help getting there!
This post is part of our Abridged series, which aims to explain the basics of some of the more ominous yet awesome Drupal projects in simple and practical terms. We hope these posts will help demystify some of these projects for people who have been hesitant to try them out!
In this post we'll take a look at the Context module.
While working on our last project I realized that we haven't used breadcrumbs in a theme for a while (well that is not entirely really true, we use them a lot for the admin section). We came across of what we first thought was a bug; the breadcrumbs weren't following the primary links herarchy and were only displaying the "Home" link.
Google here we go, search... search... read... read... read more... and after a lot of trial and error I found the the solution: Custom Breadcrumbs and Menu Breadcrumb.
Now that you have these modules installed and enabled... sorry, what? Not ready yet? Ok, let me know when you're ready... (Meanwhile, Alberto is doing important research) ........................... Huh, what was that? Installation completed? Great, then let's continue.
When we started transitioning into using an Agile development method just over a year ago, one of the first and most constant challenges we ran into was how to make it work for our clients. Agile has been a fantastic tool for defining internal processes that really work for us at Affinity Bridge. Many of our clients, being non-profit organizations and academic institutions, however, are accountable to boards who have to review and approve their budgets ahead of time. They're not able to bill according to work done during agile sprints, without having budgeted for the work ahead of time. Here are a few tips from the lessons we've learned for doing agile development while managing estimates and budgets in a way that works for our clients.
Last week, Zoe, Dave, and I made our way down to San Francisco for DrupalCon. It was a fantastic week, and even though I knew how many people were attending, I was still stunned by the actual size of the crowd, especially when we were all gathered together for the keynote sessions.
A few (well, three - I'm saying three counts as a few) people over at g.d.o asked to try out a module I wrote for a client of ours a few weeks ago. So I'm putting up the first beta of it here.
Behold, the first generation of the MailChimp Import module (Drupal 6 only). This module does no more, and no less, than import your MailChimp campaigns into your Drupal site as nodes. Why would you want to do that, when MailChimp already provides online versions of your newsletters? Because your client asks for it, that's why. Perhaps they want to be able to file their sent newsletters alongside their other content, in the system of taxonomy that suits their particular mental aesthetic. Perhaps they want website visitors to be able to find articles in their old newsletters from the search box in the header of their Drupal site. Perhaps they don't trust that cheerful monkey.