From d6851a2b204e6bf14a9bfe868d5b001e0ee422be Mon Sep 17 00:00:00 2001
From: Adam Hyde <adam@coko.foundation>
Date: Sat, 22 Jan 2022 04:37:49 +0000
Subject: [PATCH] Update ssp-editoria.md
---
src/articles/ssp-editoria.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/articles/ssp-editoria.md b/src/articles/ssp-editoria.md
index 2e79f91..0b1764d 100644
--- a/src/articles/ssp-editoria.md
+++ b/src/articles/ssp-editoria.md
@@ -92,12 +92,12 @@ category: "study-paper"
</figure>
<p class="paragraph">Components can be reordered by drag and drop. Updates to the book structure are updated in real
time so all team members see changes immediately.</p>
- <p class="paragraph"><a href=""><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
+ <p class="paragraph"><a href="/images/uploads/toc.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
<p class="paragraph">Component-level workflow states (eg ‘for review’, ‘proofing’ etc)
are also managed from the Book Builder. Each component is marked with its own state, independently of the other
components. Users with the correct permissions can change a component state (move it from one status to another).
A component state change is also updated in real time for all users.</p>
- <p class="paragraph"><a href=""><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
+ <p class="paragraph"><a href="/images/uploads/concurentstates.gif" target="_new"><img src="/images/uploads/Demo-icon2-150x150.png"/></a></p>
<p class="paragraph">Since all components have their own individual state, workflow can be optimized by enabling
each user to advance through the production process at their own pace, allowing for many different types of tasks
to occur in parallel across the entire book.</p>
--
GitLab