Who works on @SlackHQ? Here's a free AI idea. I want a summary of my day. How many threads I engaged with, how many people I shared DMs with, how many posts I made, how many channels I reviewed. I need a report that I can share about why I got nothing else done during the day. :D
@disco_lu Obviously the advice is to use the components as their built, but that I can't stop them from doing what they feel they need to do to solve a problem.
@rogie@milanseitler Slots, but without overhead of having to create a component outside of the instance structure, that would be great. Basically being able to assign a child frame (of the component) as the composition space.
@RobertJBye@figma Prototype use case is great. I had previously wished that the preview window could be docked to a side, similar to comment threads, but this is effectively the same idea. Although, docking the preview would allow for easier frame/flow hopping.
@disco_lu The correct answer is: how do you handle it in code? Looking at this, you've got several visual styles, but shared behavior. This is likely a single code component with props to handle sentiment and visual style. Therefore, option 2 is the way to go.
@HonzaTmn@figma Category pages with components on them. So Actions (button, icon button, etc), Inputs (checkbox, radio, text field), Feedback (alert, toast, action dialog), and more. The components themselves are on the canvas with a documentation frame next to them.
@jahirfiquitiva You can't be messaged, it's disabled. But also, your replies are blocked to only people you follow on the Tweet about invites. Otherwise, I would've replied to your offer for a Bluesky invite. :P
I can't be the only one who sees pending updates to components in their library and can't remember or forgot what they did. Library maintainers in @figma would likely benefit from additional actions
@efedorenko@figma Not fully automatic, but Style Organizer can scan a page and show instances of colors. You can merge manual assignments into matching tokens per color.
@figma All of your communications for Widgets in Figma say “interactive widgets for your entire team”, yet my testing is showing that only Editors with Edit access to a file can interact with them. Is this deceptive marketing or unintended behavior?
@figma I’ve looked through the help documents but don’t see a ton of clarity on exactly who can interact with Widgets. Is this just Editors? If so, that artificially limits the usefulness of something like polls which would benefit from all participants, incl Viewers, from interacting.