Recently I had the opportunity and pleasure to go to UX Ireland, a conference in Trinity College focused on designing user experience. As someone interested in making websites better for everyone, and actively studying techniques for designing user interfaces that people love, it seemed a good idea.
So you've got a project. It's going to be amazing. You've dreamed up loads of functionality and are just itching to let it loose on the world. It's going to look fantastic, and everyone on the design team is ecstatic about the proposed look and feel.
I bet this opening sounds familiar to you.
Clients sign off on designs. You build a website for them based on these designs. It looks quite like the designs, but not exactly like them. It's not your fault. It's not the client's fault. But wouldn't it be nice if you could build what the client signed off?
Why are the websites we build not exactly like what the client signs off and why is it nobody’s fault? Here’s three (good) reasons:
Welcome to Volume 2 of my adventures in learnings from the DrupalTwig Slack, a resource that continues to be the best source of (frontend) knowledge for Drupal. Again, if you haven't joined, do so. (Volume 1 is here.)
And without further ado, here's some things I've learned (or helped others to learn):