<?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/7b9b7b37423b42b5b99d40482b6ee956&quot; frameborder=&quot;0&quot; width=&quot;1658&quot; height=&quot;1243&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1243</height><width>1658</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1243</thumbnail_height><thumbnail_width>1658</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/7b9b7b37423b42b5b99d40482b6ee956-6636d2f80a20e0fa.gif</thumbnail_url><duration>653.845</duration><title>Mission One Portfolio Build and Debugging</title><description>This Loom presents a student’s Mission One portfolio and how they met each checkpoint. For checkpoint one, they created index.html with their name, profile picture, and a technical skills and experience section, showing their full page layout. For checkpoint two, they added one job experience, linked a styles.css file, and used CSS (including a max-width of 550 pixels and color and sizing adjustments for text, buttons, and images) to improve the design. For checkpoint three, they created script.js to show a welcome greeting using a template literal and also demonstrated changing it to use a visitor name via prompt, then discussed the biggest debugging challenge as styling and color effects across related elements like the “glass” button.</description></oembed>