<?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/1029fb93c2bf440ab070543b3c0a6b44&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1029fb93c2bf440ab070543b3c0a6b44-09b73e35ef56ce71.gif</thumbnail_url><duration>249.9684</duration><title>Webflow Component Workaround 🛠️</title><description>In this video, I discuss a workaround for using code blocks within Webflow components, specifically for a documentation site I&apos;m building. I explain the challenges of adding non-component elements to component slots and how I created a simple code component to address this. I also share some UX issues I&apos;ve encountered with copy-pasting in the editor. Please take a look and let me know if you have any thoughts or suggestions!</description></oembed>