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:
I'm looking forward to attending Asheville Drupal Camp this August 12th-13th at Asheville–Buncombe Technical Community College in North Carolina. If you haven’t visited Asheville before, you can expect a town that feels small but that still offers exciting food, drink, and tourist destinations.
If you want to provide a great user experience for everyone who visits your website, it has to be accessible. By ensuring a site is accessible you also make it easy to use, regardless of one’s physical or mental capabilities. But as anyone who’s had to design or build a website that complies with WCAG 2.0 Level AA guidelines (the common standard for web accessibility) will tell you, it isn’t always easy, and sometimes the problems aren’t obvious. Over the years I’ve noticed a few accessibility issues that keep popping up, so I thought I would share a few of them here so you can catch these common pitfalls on your own projects.
I arrived at DrupalCon NOLA 2016 with some clear priorities for investigation, and I didn't come away disappointed. Read on for the low-down on the most important Drupal initiatives shaping our development experience here at Kalamuna.
- 1 of 16
- next ›