Home / Drupal Stories Kick Off: My Own Drupal Story

Drupal Stories Kick Off: My Own Drupal Story

It’s no secret that Drupalists are in high demand. I’ve blogged about the need for training more Drupalers and getting to them earlier in their careers previously, but that’s just one aspect of the greater topic which merits a closer inspection as a cohesive whole.

Drupal is an open source content management framework with a rabidly helpful community of developers, many of whom have been involved in creating some of the most notable properties on the web. It’s not surprising that good Drupal developers are a highly sought after commodity, but what is it like to actually work with Drupal?

Working with Drupal

As open source content managements systems and frameworks go, Drupal is a strong technical competitor. It’s not flawless, nothing is, but its technical capabilities are largely unmatched pound for pound in terms of effort. And it’s this raw power, delivered to sitebuilders right in the user interface, that begins to bring into focus the framework as a whole. Drupal approaches building on the web from a very different angle than other tools of similar purpose. Many attempt to simplify their solution to the point that it is only useful within a certain subset of purposes, while others require significant code and understanding of tools like the command line (or CLI) to accommodate things Drupal can do out of the box. This gives Drupal a huge advantage for those looking to get a website online without needing to understand PHP, bash or other common web developer tools. It is the only toolset of significant complexity, flexibility, and power to be built with the admin user in mind, not the developer.

Drupal as a Gateway Drug

Drupal can do a lot out of the box, and there are a group of modules which extend these capabilities and are generally considered essential to the professional Drupalist, but even with all these wonderful tools, the simple truth is that no system can anticipate all the needs of all web sites all the time. The web is constantly moving, and this means Drupal is constantly moving. As part of this evolution, opportunities arise to improve and contribute to Drupal, and countless individuals have taken their first steps into programming through these opportunities. Many of these people have evolved into professional developers in their own right who have become key members of the Drupal community.

You Get What You Give

To many of us, Drupal was a hobby before it was a job. Others were forced into Drupal through a job and still ended up enthusiastic community members and contributors. Still others had a more circuitous route: through volunteering, political activism, science, or music. Whatever the route into Drupal, however diverse our backgrounds are, we are a community, and we work hard and play hard. As a member of the Drupal community I’ve seen places I’d have never had the opportunity to see otherwise. I’ve made lifelong friends and worked with some of the most brilliant people in the world, all the while solving big problems, building big sites, and learning skills I can use forever. The more you invest in the Drupal community, the more you get out of it.

To highlight the power of the Drupal community and how it changes lives, I’m embarking on a series of interviews with well known Drupalists. We’ll find out how and why they joined. What really hooked them into Drupal, and some of the highlights of their journey thus far. To kick this off I thought I’d put my own answers out there and set the stage for others to follow.

Kris gets the lowdown on Kris

Q: How did Drupal find you?
A: I was working for The Worx Company, (my parent’s company) at the time. We’d experimented a bit with the various “nuke” products and OSCommerce as well as purchasing another firm who had built their own CMS in asp. None of these had been particularly worthwhile endeavors on our part. I had spent many many hours trying to customize Postnuke’s output to be something sane (I was a bit of a front-ender in those days); it was an exercise in futility. Long story short, I think a newsletter my father was subscribed to from IBM suggested people should take a look at Drupal. These were the 4.6 days, so we downloaded it and got it up and running. The content management was robust and useful, but more importantly, we could actually theme it. Drupal’s had a stigma of always “looking like Drupal”, but from day one, it took a lot less effort than other solutions we’d tried.

It was quite a while before we discovered CCK and Views, but even so, the deal was sealed for us pretty early on.

Q: What made you stick with Drupal?
A: For myself, I’ve run a handful of community sites and sites for friends for a long time. A few of them were really image-heavy, and this lead me to find Image module. It was a fairly useful gallery style module with ImageMagick integration and those things conspired together to really get me using Drupal personally. I think the turning point on that though was when I did a couple stupid things and completely broke the development site I was building with Image module. Somehow I found James Walker’s (walkah) ICQ (I think) contact information, and he was kind enough to trouble shoot with me and help me fix it. He explained all sorts of stuff about Drupal, and really started me on the path towards learning to develop for Drupal.

Q: How has Drupal made a positive impact on your life?
A: Well, before I got involved in Drupal I was still learning PHP (guess I still am) and we attempting to build an XSL:T-based template front end for a custom CMS (that I was also learning to build). Writing a CMS is sort of a folly, and the people who do it should be commended or committed, or both. So in the sense that I didn’t end of following through on that, I probably owe Drupal a lot.

Beyond that particular anecdote, Drupal really accelerated my learning of PHP and surrounded me with amazing people who were willing to share their experience and expertise with me. Over the years, I wrote a lot of custom code. Only a small amount of it was general enough (and good enough) to be worth contributing back to the community. A great deal of my contributions revolved around CTools and I ended up becoming a co-maintainer for that module. Co-maintaining the most heavily installed module in the Drupal ecosphere taught me so much and ultimately lead to my involvement in Drupal 8 which just accelerated my own learning curve yet again.

Drupal has also introduced me to many great friends. People I talk to and interact with every single day. I’ve visited places in Europe and the US that I was unlikely to ever see otherwise and have been paid to work on a project that I really truly enjoyed and care about. I’m not sure you can ask for a better job than that.

Q: What is the coolest thing you built or did with Drupal?
A: At the beginning of the Drupal 7 cycle, I was working with Commerce Guys, and we were working on Zondervan Publishing. They’ve since redone the site, but I got to do so much CTools and Solr work during that project and it really set the tone of my work with Drupal 7. It pushed me into even more Panels work and this lead to a lot of my own contrib work for both CTools and my own module: Contextual Administration.

Q: What advice do you have for aspiring Drupalists?
A: Find your niche: site builder, developer, themer, marketer, documentation writer, trainer, whatever! Drupal has so many facets that no one can be everything to everyone. If you like caching, go cache stuff. If you like page layout, do that. If you want to make great base themes, or do great designs, or help market Drupal, then do that. If you know how to explain things, sell or market or train people in Drupal. Whatever you do though, get really good at it, learn from other people, and give back as much as you can. It’ll pay off in spades.

Q: Anything else you'd like to add?
A: First, balance the awesomeness of your crazy Drupal obsession. Helping, giving, contributing, and being part of it all is very powerful, but balance it with the rest of your life. Your health, family, friends and even some fresh air now and then all make you a better Drupalist!

Second, Drupal really is all about the community. Go to meet-ups, events, learn people’s names, talk with them, ask what they do – in Drupal and otherwise. Don’t be a wallflower. Be awesome.


Posted on by decibel.places.

By 2005, I was already a Front End developer for about 8 years, with DHTML, heavy on the JavaScript and CSS.

My clients started asking me to work on PHP applications. I worked with WordPress and Mambo (predecessor to Joomla), but I was not convinced they provided the architecture and tools for the kind of projects I was building from scratch.

I was looking for a PHP CMS framework that was less rigid. I was very interested in a project called PAWS (PHP Automatic Web Site). Then I found Drupal v 4.5.

Picking up projects from Craigslist, some clients were already asking for Drupal, some were asking for a suggestion. I built one project on D4 and then a few on D5, and some more with D6. I also worked with Joomla, OSCommerce and some other stuff. I liked Drupal the best.

In 2010 I broke into Enterprise with a project for a major ad agency for a big client. After that, there has been such demand for Drupal that I have been steadily employed as a Drupal Gun-for-Hire consultant for Enterprise clients. Some of them were Acquia clients as well.

The great part about consulting is that you learn a range of new skills with every new client and new project. My Drupal skills have matured along with my experience.

In my current role, I am managing two legacy D6 sites, and I developed a D7 platform integrating Tableau data visualizations, and I am also managing a suite of node.js applications. We are planning an upgrade of the D6 sites, as well as the general business architecture.

I know that node.js is the "cool" framework these days, but it reminds me of the early days building PHP apps. I hate making edits on multiple files for a single simple feature. I still prefer Drupal.

Posted on by p45 (not verified).

Let's be clear, highly-skilled Drupalists are in high demand. If you are one of those people (and Kris, you undoubtedly are) and already have a place inside the castle, it might well seem as if there are a glut of available jobs. But the problem is, none of them are for people who need experience to break into that highly-skilled category. To survive as a Drupal worker at all, many have to perform freelance work on small-scale sites, in which they see to every aspect of development, without ever being able to pursue the deep specialism in one area that could qualify them for a proper job. Life for us is much harder, I assure you.

Posted on by Kris Vanderwater.

I don't disagree. That being said, I think there are plenty of gigs that will help developers collect enough of the skills to get them hired full time as a Drupalist. A big part of cultivating those skills, in my opinion, is attending your local Drupal User Group, hitting camps and investing in yourself. So many Drupalists offer so much of their time and expertise for free to the community.

Find a way to take advantage of those situations. Camps are so crucial to a Drupalist's career. Meeting people in the hallways and attending sessions are invaluable. As an example of that sort of stuff I'll actually be presenting my session from DrupalCamp Colorado 2014 this Thursday in an Acquia Webinar. Come check it out, we're talking Drupal 8 Plugins.

https://ww w.acquia.com/resources/webinars/drupal-8-deep-dive-plugin-system

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.