This seems to be a bit of a hot topic on Twitter right now so here’s my take.
The definitions of designer and developer and where you draw the line between the roles is a bit of a nonsense. In reality you can’t box things like this. It’s about the individuals and what skills they have and what fits your team. Overlaps in skills are not a problem, gaps are. So, the handover points will naturally surface out of what works for the team. That said, I do have some more specific thoughts about what might kinds of coding might empower a designer.
Knowing some basic DOM manipulation techniques can really help to add some life and interaction to designs – “Interaction Design”.
- Being able to select a DOM element with
document.querySelector()is a good starting point.
- Basic event handling with
.addEventListener('click', handler)is useful as it allows you to add actions.
- Handling events means learning how to write a very basic named function.
- Finally being able to toggle properties like
disabledor add/remove/toggle items from
classListenables you to design for lots of different states within the same document.
I think just these few basic steps will enable a designer to achieve a lot more in their designs.