diff --git a/src/routes/why-svelteplot/+page.md b/src/routes/why-svelteplot/+page.md index 8804dc69..b0fb163b 100644 --- a/src/routes/why-svelteplot/+page.md +++ b/src/routes/why-svelteplot/+page.md @@ -3,7 +3,7 @@ title: Why SveltePlot? description: Why do we need yet another Svelte visualization framework? --- -SveltePlot combines the concise API and concepts of Observable Plot with Svelte reactivity. It is not just a Svelte-wrapper, but re-implemented from scratch on top of D3. But what makes SveltePlot better than the existing visualization frameworks in Svelte? +SveltePlot combines the concise API and concepts of [Observable Plot](https://observablehq.com/plot/) with [Svelte](https://svelte.dev/) reactivity. It is not just a Svelte-wrapper, but re-implemented from scratch on top of [D3](https://d3js.org/). But what makes SveltePlot better than the existing visualization frameworks in Svelte? ## Layered grammar of graphics @@ -93,7 +93,7 @@ You can think of marks as the building blocks for your visualizations -- or the [fork](https://svelte.dev/playground/b329bb028a5445ba8f884291f0475be6?version=5) -This makes it a lot easier to iterate over different ideas for visualizations. For instance, if we want to combine the dot plot above with a line chart, we can just throw in a Line mark as extra layer. +This makes it a lot easier to iterate over different ideas for visualizations. For instance, if we want to combine the dot plot above with a line chart, we can just throw in a [Line mark](/marks/line) as extra layer. ```svelte live