New article, hot off the press. "Advanced Scroll Effects in Framer". Parallax, dynamic headers, and scroll driven video – find out how to take your scroll interactions to the next level in @framer. And learn to code in the process. https://t.co/AY3bDnK0Zl
@framer Styles IO was submitted to @framer for review a couple of weeks back. I'm expecting it to pop up in the Marketplace anytime soon. Keep an eye out for it under free plugins. And why not read this https://t.co/GmDLGAq8w8 while you're waiting.
Join Supernova for a panel all about components 🧱 on Thurs, November 16 at 9am PST / 6pm CET.
Featuring industry experts:
🔹Alissa Engstrom (Senior Product Designer, Design Systems at https://t.co/KLFglysK29)
🔹 @blvdmitry (Principal Frontend Engineer at https://t.co/8EPJ84AzjM)
🔹 @Giles_Perry (Director of Product Design at Skyscanner)
During this panel, you'll learn best practices for managing a component's lifecycle:
🔹 Building new components
🔹 Tracking component health
🔹 Deprecating components
We'll also dive into how designers and developers approach and leverage components.
@disco_lu@HonzaTmn@figma Given you have "Primitive: Sizes" collection, I'm guessing you have a separate "Primitive: Colours" collection. Any benefits of this approach over a single "Primitives" collection containing groups for "Colours" and "Sizes"?
@HonzaTmn@figma Primitives can be in their own collection but semantic and component variables need to be in the same collection so they can have common Day and Night modes.