<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/5417c5380a24471ba457e72598459a82&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5417c5380a24471ba457e72598459a82-1701099569077.gif</thumbnail_url><duration>165.86666666666662</duration><title>Implementing a button components with a utility-first approach into Toddle</title><description>Hi, my name is Alfred and I&apos;m new to the title tool and community. I have some considerations and questions about implementing button components into a title. I&apos;m looking for guidance on how to structure and make components more dynamic, especially when a button component can cover multiple use cases. I&apos;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.</description></oembed>