From 0082957d5fc2becb44d46d693ca67a358dc7ee79 Mon Sep 17 00:00:00 2001 From: Richard Harris Date: Sun, 10 Mar 2019 08:44:42 -0400 Subject: [PATCH] fix docs links --- ...12-31-sapper-towards-the-ideal-web-app-framework.md | 4 ++-- site/content/blog/2018-04-18-version-2.md | 4 ++-- site/content/guide/02-template-syntax.md | 4 ++-- site/content/guide/03-scoped-styles.md | 4 ++-- site/content/guide/05-nested-components.md | 2 +- site/content/guide/06-special-components.md | 2 +- site/content/guide/07-events.md | 2 +- site/content/guide/08-bindings.md | 2 +- site/content/guide/15-server-side-rendering.md | 6 +++--- site/content/guide/16-state-management.md | 4 ++-- site/content/guide/18-advanced.md | 8 ++++---- site/content/guide/19-custom-elements.md | 2 +- site/content/guide/98-api-reference.md | 10 +++++----- site/src/components/Repl/Output/index.svelte | 2 +- site/src/routes/docs/_GuideContents.svelte | 4 ++-- site/src/routes/docs/_sections.js | 2 +- 16 files changed, 31 insertions(+), 31 deletions(-) diff --git a/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md b/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md index 0f6266a4d1..614f266136 100644 --- a/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md +++ b/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md @@ -48,7 +48,7 @@ What happens if we use the new model as a starting point? ## Introducing Sapper - + [Sapper](https://sapper.svelte.technology) is the answer to that question. **Sapper is a Next.js-style framework that aims to meet the eleven criteria at the top of this article while dramatically reducing the amount of code that gets sent to the browser.** It's implemented as Express-compatible middleware, meaning it's easy to understand and customise. @@ -67,7 +67,7 @@ But size is only part of the story. Svelte apps are also extremely performant an The biggest drawback for many developers evaluating Sapper would be 'but I like React, and I already know how to use it', which is fair. -If you're in that camp, I'd invite you to at least try alternative frameworks. You might be pleasantly surprised! The [Sapper RealWorld](https://github.com/sveltejs/realworld) implementation totals 1,201 lines of source code, compared to 2,377 for the reference implementation, because you're able to express concepts very concisely using Svelte's template syntax (which [takes all of five minutes to master](https://svelte.technology/guide#template-syntax)). You get [scoped CSS](the-zen-of-just-writing-css), with unused style removal and minification built-in, and you can use preprocessors like LESS if you want. You no longer need to use Babel. SSR is ridiculously fast, because it's just string concatenation. And we recently introduced [svelte/store](https://svelte.technology/guide#state-management), a tiny global store that synchronises state across your component hierarchy with zero boilerplate. The worst that can happen is that you'll end up feeling vindicated! +If you're in that camp, I'd invite you to at least try alternative frameworks. You might be pleasantly surprised! The [Sapper RealWorld](https://github.com/sveltejs/realworld) implementation totals 1,201 lines of source code, compared to 2,377 for the reference implementation, because you're able to express concepts very concisely using Svelte's template syntax (which [takes all of five minutes to master](https://svelte.technology/docs#template-syntax)). You get [scoped CSS](the-zen-of-just-writing-css), with unused style removal and minification built-in, and you can use preprocessors like LESS if you want. You no longer need to use Babel. SSR is ridiculously fast, because it's just string concatenation. And we recently introduced [svelte/store](https://svelte.technology/docs#state-management), a tiny global store that synchronises state across your component hierarchy with zero boilerplate. The worst that can happen is that you'll end up feeling vindicated! But there are trade-offs nonetheless. Some people have a pathological aversion to any form of 'template language', and maybe that applies to you. JSX proponents will clobber you with the 'it's just JavaScript' mantra, and therein lies React's greatest strength, which is that it is infinitely flexible. That flexibility comes with its own set of trade-offs, but we're not here to discuss those. diff --git a/site/content/blog/2018-04-18-version-2.md b/site/content/blog/2018-04-18-version-2.md index 3204fa1035..295efbbd11 100644 --- a/site/content/blog/2018-04-18-version-2.md +++ b/site/content/blog/2018-04-18-version-2.md @@ -86,7 +86,7 @@ If you need to support IE11 and friends, you will need to use a transpiler like ## New lifecycle hooks -In addition to `oncreate` and `ondestroy`, Svelte v2 adds two more [lifecycle hooks](guide#lifecycle-hooks) for responding to state changes: +In addition to `oncreate` and `ondestroy`, Svelte v2 adds two more [lifecycle hooks](docs#lifecycle-hooks) for responding to state changes: ```js export default { @@ -169,7 +169,7 @@ This change might seem annoying initially, but it's the right move: among other ## event_handler.destroy -If your app has [custom event handlers](guide#custom-event-handlers), they must return an object with a `destroy` method, *not* a `teardown` method (this aligns event handlers with the component API). +If your app has [custom event handlers](docs#custom-event-handlers), they must return an object with a `destroy` method, *not* a `teardown` method (this aligns event handlers with the component API). ## No more type coercion diff --git a/site/content/guide/02-template-syntax.md b/site/content/guide/02-template-syntax.md index 339739c060..d915a8e37f 100644 --- a/site/content/guide/02-template-syntax.md +++ b/site/content/guide/02-template-syntax.md @@ -176,7 +176,7 @@ You can access the index of the current element with *expression* as *name*, *in } ``` -> By default, if the list `a, b, c` becomes `a, c`, Svelte will *remove* the third block and *change* the second from `b` to `c`, rather than removing `b`. If that's not what you want, use a [keyed each block](guide#keyed-each-blocks). +> By default, if the list `a, b, c` becomes `a, c`, Svelte will *remove* the third block and *change* the second from `b` to `c`, rather than removing `b`. If that's not what you want, use a [keyed each block](docs#keyed-each-blocks). You can use destructuring patterns on the elements of the array: @@ -237,7 +237,7 @@ If the expression in `{#await expression}` *isn't* a promise, Svelte skips ahead ### Directives -Directives allow you to add special instructions for adding [event handlers](guide#event-handlers), [bindings](guide#bindings), [transitions](guide#transitions) and so on. We'll cover each of those in later stages of this guide – for now, all you need to know is that directives can be identified by the `:` character: +Directives allow you to add special instructions for adding [event handlers](docs#event-handlers), [bindings](docs#bindings), [transitions](docs#transitions) and so on. We'll cover each of those in later stages of this guide – for now, all you need to know is that directives can be identified by the `:` character: ```html diff --git a/site/content/guide/03-scoped-styles.md b/site/content/guide/03-scoped-styles.md index 9a96da84db..b9ba69b981 100644 --- a/site/content/guide/03-scoped-styles.md +++ b/site/content/guide/03-scoped-styles.md @@ -30,7 +30,7 @@ Open the example above in the REPL and inspect the element to see what has happe This is vastly simpler than achieving the same effect via [Shadow DOM](http://caniuse.com/#search=shadow%20dom) and works everywhere without polyfills. -> Svelte will add a `