Late last year, we upgraded our blog from Drupal 7 to Drupal 8. Our main objective was to invest in our skills within Kalamuna so we could, in turn, better serve our clients. We have a lot of Drupal 8 migrations lined up over the course of the next year or so, and we foresee many more coming down the pipeline. This gave us a chance to learn the ins and outs of Drupal 8, with the added value of sprucing up our very own blog. This post is a summary of takeaways from our experience that I hope will help you on your own Drupal 8 adventures.
Every year I try to attend as many industry conferences as possible, but over the years I’ve become more selective about which ones I go to. I find them to be incredibly valuable and insightful, but they also cost money and take time, so I grade them pretty hard. This year I had the pleasure of attending several UX-focused conferences. Each was great in different ways, and I came away leaving inspired each time, and wanting to share some of the lessons I learned, so I wrote this blog post.
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.
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?
Creating a website can be likened to making a custom car or house, but with a few quirks. A website is not only supposed to be an efficiency-enhancing tool for the person or organization that paid for it, but also a reflection of the organization's persona and agenda. Creating a visual and interactable representation of these concepts takes a significant amount of creativity and testing. The job of any web shop should be to work extensively with clients to pull out exactly what the group's goals and needs are for the web and to translate them for the internet.
We here at Kalamuna believe in the power in science, and aren't in the business of making leaps of faith in regards to web development. We try to avoid superficial "let's hope for the best" scenarios with all projects, and aren't interested in putting ourselves or our clients in painful situations.