Update ssp-kotahi.md

src/articles/ssp-kotahi.md

@@ -183,7 +183,9 @@ src="/images/uploads/sspKotahi-06.png">
 is additional information about the manuscript (this is set via the Form Builder, see below).</p>
 <p class="paragraph">The reviewer can then accept or reject the invitation via their Dashboard (soon also via the
 email). The Reviewer can then access the manuscript, filtered submission data, and the review form via the
-Dashboard. The Review Page has a section for writing the review and attaching files:</p>
+Dashboard. </p>
+      <p class="paragraph"><a href="https://gitlab.coko.foundation/kotahi/kotahi/-/wikis/uploads/a83e723e0fbd4f2219cf5b1fc4b96685/Screencast_01-12-2021_07_08_00_PM.webm" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
+<p>The Review Page has a section for writing the review and attaching files:</p>
 <p class="paragraph"></p>
 <figure><img
 src="/images/uploads/sspKotahi-07.png">
@@ -193,6 +195,7 @@ src="/images/uploads/sspKotahi-07.png">
 <p class="paragraph">When reviews are complete, the HE can access the reviews via the Control Panel for the
 manuscript and decide on whether to accept, reject, or request a revision. Secondary revision types are managed
 through email templates (see below).</p>
+      <p class="paragraph"><a href="/images/uploads/reviews.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
 <p class="paragraph">The HE can write their response to the author in the panel provided. The text is shown to the
 author on the submission form (connected to versions, see below).</p>
 <p class="paragraph">The author can then revise both the submission data and the manuscript and resubmit. The
@@ -230,6 +233,7 @@ src="/images/uploads/sspKotahi-10.png">
 <p class="paragraph">Submissions are managed per revision round. Each round creates a new version of both the
 submission data and the manuscript attachments/internal content store. Revision history can be browsed by authors
 and editorial staff alike. Earlier versions cannot (of course) be edited.</p>
+      <p class="paragraph"><a href="/images/uploads/versions.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
 <h3>Single Source Publishing</h3>
 <p class="paragraph">If docx files are submitted, Kotahi can be a complete end-to-end <a
 href="https://coko.foundation/single-source-publishing/" rel target="blank">Single Source Publishing</a> System.
@@ -258,9 +262,11 @@ tagging of each field with unique IDs (useful for building JATS/XML at export ti
 be shown to reviewers when inviting them to review, controlling taxonomy, identifying which columns are displayed
 on the Manuscripts Page, and it can even be used to extend the Control Panel UI. The Form Builder will
 increasingly become an central part of the Kotahi platform. Form Builders are much underestimated.</p>
+      <p class="paragraph"><a href="/images/uploads/form.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
 <h3>Reports</h3>
 <p class="paragraph">Reports are integrated into Kotahi and are pretty comprehensive. We have opted for dynamic
 rendering to improve the user enjoyment of the Kotahi UI.</p>
+      <p class="paragraph"><a href="/images/uploads/Kotahi-summary-report4-1.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
 <h3>&#xA0;Workflow Configuration</h3>
 <p class="paragraph">There are immense workflow configuration options. So far, almost all are via config files but
 we have a UI config manager design. While we will use the above workflow, the following are two workflow examples