From e443ccea85c10ca22b8582d5aafbd11a831d63a9 Mon Sep 17 00:00:00 2001 From: silvester-pari Date: Thu, 1 Feb 2024 16:58:22 +0100 Subject: [PATCH] chore: relative paths --- public/demo/scrollytelling.md | 24 ++++++++++++------------ src/stories/StoryTelling.stories.js | 2 +- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/public/demo/scrollytelling.md b/public/demo/scrollytelling.md index ddaca44..9edca03 100644 --- a/public/demo/scrollytelling.md +++ b/public/demo/scrollytelling.md @@ -40,17 +40,17 @@ Every story you read here originates from a Markdown file. Why Markdown? It's a Markdown allows us to structure our text without getting bogged down in complex code, making it accessible to a broad audience. -![](/demo/md-1.png) +![](./demo/md-1.png) The markdown file is structured into sections (think of them as the "story blocks"), and, optionally, into individual steps within those sections. -![](/demo/md-2.png) +![](./demo/md-2.png) But it's not just about convenience in writing—Markdown comes with an extra perk. When we host our Markdown files on GitHub, the platform automatically renders them. This means we get a neatly formatted, readable story without any additional effort. So, from the simplicity of writing to the seamless rendering on platforms like GitHub, Markdown plays a crucial role in bringing these stories to our readers effortlessly. -![](/demo/md-3.png) +![](./demo/md-3.png) ---

Embeddable external Blocks

@@ -258,7 +258,7 @@ The story rendering can be adapted to fit the look & feel of the application usi "body-font-family": "'Mukta', sans-serif", ``` -![](/demo/branding-1.png) +![](./demo/branding-1.png) ---