As a Drupal developer, you may believe your spirit animal burrows somewhere between Drupal 7 and Drupal 8. Mine resides in Backdrop. Let me tell you how I discovered it there. I saw Jen Lampton give a great session on Backdrop for the first time at Florida DrupalCamp 2014 and I really didn’t give it much thought. People were still yammering on about Drupal 8 and no one was adopting anything at the time. We were still trying to get people on Drupal 7. Flash forward to Spring 2016: Kalamuna won a small project through a nonprofit client in the San Francisco Bay Area. My dilemma: build the tiny site in Drupal 8, or do it with Drupal 7 (Panopoly and Kalatheme) — or go with Backdrop. I thought about it for a week and I landed on Backdrop. Here’s why:
Greetings readers. I’m a Senior Developer and Support Manager at Kalamuna. My main job is to de-jankify websites we inherit in the support universe. To do this, I’ve had to continue to teach myself how to debug sites. I was thrown into Drupal about 6 years ago and have stuck with it since. In that time, I’ve tried many different debugging tools and methods. Lucky for you, I found what works and what doesn’t. Below you’ll see what I’ve found to be the easiest and quickest way to debug Drupal Sites.
As a professional at a higher education institution, how can you find Drupal resources on campus and use them to super-power your website? Familiarity with these people can make the difference between a successful and a failed project. In this post I outline a few easy ways to start finding what you need to use Drupal at your university.
It's that time of year again, when Drupal developers from far and wide come to take advantage of the lingering California summer and revel in Drupal nirvana at the Bay Area Drupal Camp (aka "BADCamp").
Drupal 8 is here. Almost. As a marketing or IT leader at your university you’ve got enough to worry about. Let’s hold hands.
As a veteran entrepreneur, self-taught coder and Kalamuna’s Support Manager and a senior developer, I’ve been around more than “a block or two.” With so many of you kids getting into development, I figured I would try to make my humble mark on this planet by throwing out my take on the kind of mentality that can help someone thrive in our field. So here’s my story (abridged!) and a few tips on how to think about work.
A long time ago in a galaxy not too far away, I supported myself through college (and then some) by waiting tables. It was a lot of fun and good cardio, but not the kind of thing that I thought would look good on a resume when my aim was to leave the hospitality business. But nothing could be further from the truth. I learned important life lessons, including how to manage my time, work under pressure, and feel more empathy for people. Waiting tables prepared me for my professional career far better than all of the internships I had over my collegiate career.
I might be completely alone in this, but the support desk is one of my favorite aspects of my job. It’s the instant-gratification of web development. Receive a request, solve a problem, and BOOM: happy client! Every time I close out a ticket, I feel like I’ve made a client’s life just a little bit easier. So here’s a few tips to help support clients return the favor:
A long time ago, in an agency far, far away… Darth Salesman has just handed over a long-winded statement of work to the green project manager and beleaguered discovery team. Confusion and despair ensue. How is the team supposed to know exactly how to proceed? What kind of promises, parameters and expectations were made beforehand? What tone should they take as they work with the client? How can we bridge the gap between the sales process and discovery phase?