<?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/3500cec4bf604d768edbe0a0e74fa45e&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/3500cec4bf604d768edbe0a0e74fa45e-d7c349760c0ce83b.gif</thumbnail_url><duration>225.577</duration><title>Improving Template Management in NoLoco</title><description>In this video, I discuss the challenges we face with managing templates in NoLoco, particularly how it affects both developer and user experiences. I provide an example involving a single record template for user profiles and the complexities that arise when trying to maintain a single source of truth. I propose two potential solutions to improve this situation and would love to hear your thoughts on our roadmap moving forward.</description></oembed>