My Drupal journey started some five years ago, and it is now about to end. It's been a fantastic journey.
A year ago I started studying to become a school teacher in maths and physics. While studying it became clear to me that teaching and Drupal are two passions that are so big that they don't fit in my head at the same time, and while Drupal is one of the most fun and engaging things I know, the competition from teaching and education was just overwhelming. I know that teaching and education is what I want to dedicate my professional life to, and if that means stop doing Drupal then so be it.
This week I posted the last episode of the epic learning series "Four weeks of Drupal". It contains 99 parts, from "What is Drupal?" to "Providing new entity properites" and can be found over at the NodeOne learning library. This will be my final Drupal learning series, and it feels good to end with (IMHO) best and most comprehensive of the learning series I've created.
DrupalCon — there's hardly a better time or place to try your hand at contributing to the Drupal project. Yesterday I went down to Wunderkraut's contribution lounge to see my good friend and colleague dixon_ and ask him for advice on where to start with code contribution. He showed me an easy way to dig right in by reviewing other people's work using sun's Dreditor user script, and I was so excited (it's much easier than I thought!) that I couldn't resist sharing it with you as well!
Did you know that NodeStream changed from its initial intention to be an online magazine publishing distribution? This is something we at NodeOne have worked on for a while and internally we actually use NodeStream as a base for all our client projects. We think NodeStream is mature enough to become a base for more peoples project and we plan to support you with it.
Earlier this week, I was privileged to attend the Future of Web Design conference in London together with my colleague, Mattias Johansson. With world class speakers running sessions on two tracks for two days, my expectations for this event was huge. In retrospect, it turns out it could have been even higher. I was blown away.
On NodeOne we use Features a lot. Mostly for exporting configuration, and we have some problems with that. Some of the stuff that you want to do, is not in Features, sometimes we need to solve it in another way - mostly with code in the installation profile, but some other issues just keep hanging lose.
I, along with 12 other NodeOners, spent a 3-day weekend in beautiful Amsterdam attending Frontend United. A brand-new concept, Frontend United (FU), replaces Drupal Design Camp as the conference to attend for anyone interested in design and UX related to Drupal.
You should work with coding standards in mind, it is a very good thing when you share you things with other developers. And there tools out there to help you with the standards, for me that is the Drupal Coding Standards.