From 90e69ab5df33b92cb8fe1b1727df7fd06a0383a6 Mon Sep 17 00:00:00 2001 From: begueradj Date: Tue, 19 Feb 2019 18:02:32 +0200 Subject: [PATCH] Fixed typo --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index d5792e8a..258b3f5e 100644 --- a/docs/README.md +++ b/docs/README.md @@ -38,7 +38,7 @@ Before using SSR for your app, the first question you should ask is whether you ## SSR vs Prerendering -If you're only investigating SSR to improve the SEO of a handful of marketing pages (e.g. `/`, `/about`, `/contact`, etc), then you probably want __prerendering__ instead. Rather than using a web server to compile HTML on-the-fly, prerendering simply generates static HTML files for specific routes at build time. The advantage is setting up prerendering is much simpler and allows you to keep your frontend as a fully static site. +If you're only investigating SSR to improve the SEO of a handful of marketing pages (e.g. `/`, `/about`, `/contact`, etc), then you probably want __prerendering__ instead. Rather than using a web server to compile HTML on-the-fly, prerendering simply generates static HTML files for specific routes at build time. The advantage in setting up prerendering is much simpler and allows you to keep your frontend as a fully static site. If you're using webpack, you can easily add prerendering with the [prerender-spa-plugin](https://github.com/chrisvfritz/prerender-spa-plugin). It's been extensively tested with Vue apps - and in fact, [the creator](https://github.com/chrisvfritz) is a member of the Vue core team.