β¨ Follow for posts on UX and Accessibility β‘ Product Designer π Driving usability and business impact through data-driven insights and accessibility expertise
@hamishoneill We have a boilerplate design file which all designers duplicate when they start a new task. We have master component templates set up in there for common breakpoints with headers/footers/grids etc. Then detach and off you go
@hamishoneill The other problem I have with slots is that if theyβre part of a component with variants, then nested inside a larger parent pattern, which also has variants. The instance swap isnβt retained when changing variants of that parent pattern, which is a bad consumer experience
Is anyone else a bit worried about the level of complexity creeping into Figma?
Balancing "make design accessible" with constant feature requests from a vocal power user base has to be TOUGH...
FWIW I think they're doing great. But each Config they steepen the learning curve π€·ββοΈ
@jesseddy@figma You're welcome! Alternatively for small jobs, you could keep both light/dark in the same file as variants or separate instances which could be easily swapped out.
@zeroheight Draft a strategy how you want your consumers to adopt your design system. Talk to them often an early to establish commitment to adoption, then shift the conversation to how much to adopt and how soon.
@Amy_Hupe Most def cheese and onion pasty. I'd be too distracted to get annoyed at the other with my breath taken away from the pong. You need a loud crunchy snack to level up the annoyance