{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5417c5380a24471ba457e72598459a82\" frameborder=\"0\" width=\"1728\" height=\"1296\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1296,"width":1728,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1296,"thumbnail_width":1728,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5417c5380a24471ba457e72598459a82-1701099569077.gif","duration":165.86666666666662,"title":"Implementing a button components with a utility-first approach into Toddle","description":"Hi, my name is Alfred and I'm new to the title tool and community. I have some considerations and questions about implementing button components into a title. I'm looking for guidance on how to structure and make components more dynamic, especially when a button component can cover multiple use cases. I'm also unsure about the right moment to split components. I hope someone can help me figure out the best approach for implementing a component with different attributes for different users."}