Improved markdown container image/video display. Added more content to a project.

data/content.ts

@@ -124,24 +124,67 @@ An \`agent\` is a real-person (and most often a representative of some business)
 A front-desk employee at a hotel checking in a guest is an easy to reach example. The ticketing/admission agents at an event might be another.
 These agent to guest interactions are what drive an organization on the ground. 
 
-These interactions might occur at high volumes and might be sustained throughout normal business operation. In such cases,
-the amount of time spent completing tasks and exchanging information might have a very high impact on a business' operations.
+
+<blockquote>A standard conversation flow
+<a target="_blank" href="/img/projects/fam/standard-conversation-flow.png">
+<img src="/img/projects/fam/standard-conversation-flow.png" alt="Alt text" />
+</a>
+</blockquote>
+  
+
+These interactions might repeat throughout normal business operation, and more than one may happen at once. Agents can
+(in general) only handle one interaction at a time.
+
+
+<blockquote>A line of workflows waiting to happen
+<a target="_blank" href="/img/projects/fam/flow-lineup.png">
+<img src="/img/projects/fam/flow-lineup.png" alt="Alt text" />
+</a>
+</blockquote>
+  
+
+Scale this up. Hundreds of guests, or thousands of guests arriving at a high rate. A once a year event is happening or somesuch. 
+Most organizations at such scale aren't going to have a single agent handling any task that might be a bottleneck to normal operation.
+
+
+<blockquote>An surge of workflows happening all at once
+<a target="_blank" href="/img/projects/fam/flow-lineup-at-scale.png">
+<img src="/img/projects/fam/flow-lineup-at-scale.png" alt="Alt text" />
+</a>
+</blockquote>
+
+With or without the additional help, at scale, little variances in the amount of time spent in every component of an interaction while
+completing tasks and exchanging information might have a very high cumulative impact on a business' ability to scale operation to bursts in demand.
 
 FAM supports breaking these interactions down into streamlined, consistent, efficient, repeatable, and flexible 
 workflows. 
 
-<blockquote>Not every interaction will be the same. Some guests might have additional service needs. 
-<a target="_blank" href="/img/projects/fam/reference-1.png">
-<img src="/img/projects/fam/reference-1.png" alt="A workflow, and a workload." width="800"/> 
+
+<blockquote>
+<a target="_blank" href="/img/projects/fam/workflow-steps.png">
+<img src="/img/projects/fam/workflow-steps.png" alt="A workflow divides some business process into a sequence of steps." width="800"/> 
 </a>
 </blockquote>
 
+<blockquote>
+<a target="_blank" href="/img/projects/fam/workflow-abandon.png">
+<img src="/img/projects/fam/workflow-abandon.png" alt="A workflow is easy to repeat or abandon." width="800"/> 
+</a>
+</blockquote>
 
+<blockquote>
+<a target="_blank" href="/img/projects/fam/workflow-sequence-trav.png">
+<img src="/img/projects/fam/workflow-sequence-trav.png" alt="A workflow may allow traversal between steps." width="800"/> 
+</a>
+</blockquote>
 
-There is a minimum amount of time that it takes an agent to complete a task in any software, and there is a reasonable maximum amount of time that might be spent on
-unusual circumstances or perhaps lost to the 'growing pains' of inexperienced staff or imperfect systems.
+There is a minimum amount of time that it takes an agent to complete a task in a UI and a reasonable maximum amount of time that might
+ be spent on the same task in the same UI. This variance could be blamed on various factors, but it's mostly just input errors or mistakes in procedure.
 
-FAM tries to shorten the duration of agent to guest interactions without reducing the quality of the interaction through purpose-built UX-first guided workflows. Task identification from business analysis are made into functional workflows that support reducing the time taken to complete tasks while also addressing the variability in 
+FAM tries to reduce the amount of time lost to mistakes and the overall interaction duration without reducing the quality of the interaction 
+through purpose-built UX-first guided workflows.
+
+Task identification from business analysis are made into functional workflows that support reducing the time taken to complete tasks while also addressing the variability in 
 how much time that it takes to complete these tasks. 
 
 
@@ -152,7 +195,11 @@ how much time that it takes to complete these tasks.
 </blockquote>
 
 
-A step can contain any type of work, and can be used in multiple workflows. An identification step for a check-in process using the default template might look like such:
+A step can contain any type of work, and can be used in multiple workflows.
+
+
+An identification step for a check-in process using the default template might look like such:
+
 
 <blockquote>The general look and feel of a step in a workflow. 
 <a target="_blank" href="/img/projects/fam/example-step.png">

styles/markdown-container.css

@@ -38,7 +38,23 @@
         text-align: center;
         font-family: var(--sans);
         font-size: 12;
+        line-height: 2;
         color: var(--muted);
+        background-color: var(--bg-raised);
+        padding: 0.5em;
+        border-radius: var(--radius-md);
+        box-shadow: var(--shadow-md);
+        display: flex;
+        flex-direction: column-reverse;
+        margin-bottom: 2em;
+        
+    }
+
+    blockquote img {
+        border-radius: var(--radius-sm);
+    }
+    blockquote video {
+        align-self: center;
     }
 
     ul {