Deployed 8c21368 to main with MkDocs 1.5.3 and mike 2.0.0

main/demo/AliceGetsAPhone/index.html

@@ -2269,24 +2269,24 @@ <h4 id="waiting-for-the-faber-agent-to-start">Waiting for the Faber agent to sta
 <p>As part of its startup process, the agent will publish a revocation registry to the ledger.</p>
 <details>
     <summary>Click here to view screenshot of the revocation registry on the ledger</summary>
-    <img src="collateral/revocation-2-ledger.png" alt="Ledger">
+    <img src="../collateral/revocation-2-ledger.png" alt="Ledger">
 </details>
 
 <h2 id="accept-the-invitation">Accept the Invitation<a class="headerlink" href="#accept-the-invitation" title="Permanent link">&para;</a></h2>
 <p>When the Faber agent starts up it automatically creates an invitation and generates a QR code on the screen. On your mobile app, select "SCAN CODE" (or equivalent) and point your camera at the generated QR code. The mobile agent should automatically capture the code and ask you to confirm the connection. Confirm it.</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-1-connect-1.jpg" alt="Accept Invitation">
+    <img src="../collateral/S-1-connect-1.jpg" alt="Accept Invitation">
 </details>
 
 <p>The mobile agent will give you feedback on the connection process, something like "A connection was added to your wallet".</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-1-connect-2.jpg" alt="Add Connection to Wallet">
+    <img src="../collateral/S-1-connect-2.jpg" alt="Add Connection to Wallet">
 </details>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-1-connect-3.jpg" alt="Add Connection to Wallet">
+    <img src="../collateral/S-1-connect-3.jpg" alt="Add Connection to Wallet">
 </details>
 
 <p>Switch your browser back to Play with Docker. You should see that the connection has been established, and there is a prompt for what actions you want to take, e.g. "Issue Credential", "Send Proof Request" and so on.</p>
@@ -2302,7 +2302,7 @@ <h2 id="issue-a-credential">Issue a Credential<a class="headerlink" href="#issue
 <p>In the Faber console, select option <code>1</code> to send a credential to the mobile agent.</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-3-credential-0.png" alt="Issue Credential">
+    <img src="../collateral/S-3-credential-0.png" alt="Issue Credential">
 </details>
 
 <p>The Faber agent outputs details to the console; e.g.,</p>
@@ -2316,38 +2316,38 @@ <h3 id="accept-the-credential">Accept the Credential<a class="headerlink" href="
 <p>The credential offer should automatically show up in the mobile agent. Accept the offered credential following the instructions provided by the mobile agent. That will look something like this:</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-3-credential-1.jpg" alt="Credential Offer">
+    <img src="../collateral/S-3-credential-1.jpg" alt="Credential Offer">
 </details>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-3-credential-2.jpg" alt="Credential Details">
+    <img src="../collateral/S-3-credential-2.jpg" alt="Credential Details">
 </details>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-3-credential-3.jpg" alt="Credential Acceptance">
+    <img src="../collateral/S-3-credential-3.jpg" alt="Credential Acceptance">
 </details>
 
 <h2 id="issue-a-presentation-request">Issue a Presentation Request<a class="headerlink" href="#issue-a-presentation-request" title="Permanent link">&para;</a></h2>
 <p>We will use the Faber console to ask mobile agent for a proof. This could be done using the Swagger API, but we'll leave that as an exercise to the user.</p>
 <p>In the Faber console, select option <code>2</code> to send a proof request to the mobile agent.</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-4-proof-0.png" alt="Request Proof">
+    <img src="../collateral/S-4-proof-0.png" alt="Request Proof">
 </details>
 
 <h2 id="present-the-proof">Present the Proof<a class="headerlink" href="#present-the-proof" title="Permanent link">&para;</a></h2>
 <p>The presentation (proof) request should automatically show up in the mobile agent. Follow the instructions provided by the mobile agent to prepare and send the proof back to Faber. That will look something like this:</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-4-proof-1.jpg" alt="Proof Request Notice">
+    <img src="../collateral/S-4-proof-1.jpg" alt="Proof Request Notice">
 </details>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-4-proof-2.jpg" alt="Proof Request Details">
+    <img src="../collateral/S-4-proof-2.jpg" alt="Proof Request Details">
 </details>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-4-proof-3.jpg" alt="Proof Presentation">
+    <img src="../collateral/S-4-proof-3.jpg" alt="Proof Presentation">
 </details>
 
 <p>If the mobile agent is able to successfully prepare and send the proof, you can go back to the Play with Docker terminal to see the status of the proof.</p>
@@ -2356,15 +2356,15 @@ <h2 id="review-the-proof">Review the Proof<a class="headerlink" href="#review-th
 <p>In the Faber console window, the proof should be received as validated.</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/S-4-proof-4.png" alt="Proof Validation">
+    <img src="../collateral/S-4-proof-4.png" alt="Proof Validation">
 </details>
 
 <h2 id="revoke-the-credential-and-send-another-proof-request">Revoke the Credential and Send Another Proof Request<a class="headerlink" href="#revoke-the-credential-and-send-another-proof-request" title="Permanent link">&para;</a></h2>
 <p>If you have enabled revocation, you can try revoking the credential and publishing its pending revoked status (<code>faber</code> options <code>5</code> and <code>6</code>). For the revocation step, You will need the revocation registry identifier and the credential revocation identifier (which is 1 for the first credential you issued), as the Faber agent logged them to the console at credential issue.</p>
 <p>Once that is done, try sending another proof request and see what happens! Experiment with immediate and pending publication. Note that immediate publication also publishes any pending revocations on its revocation registry.</p>
 <details>
     <summary>Click here to view screenshot</summary>
-    <img src="collateral/revocation-3-console.png" alt="Revocation">
+    <img src="../collateral/revocation-3-console.png" alt="Revocation">
 </details>
 
 <h2 id="send-a-connectionless-proof-request">Send a Connectionless Proof Request<a class="headerlink" href="#send-a-connectionless-proof-request" title="Permanent link">&para;</a></h2>