From 050df94f0d2d1bd29138dabb9beaf2f27ec5b9f9 Mon Sep 17 00:00:00 2001 From: Romuald Brillout Date: Fri, 1 Mar 2024 19:20:15 +0100 Subject: [PATCH] docs: further mention the #1476 ticket/workaround (#1529) --- docs/pages/pre-rendering/+Page.mdx | 6 ++++++ docs/pages/pre-rendering/PreRenderDynamicRoutes.mdx | 2 +- docs/pages/prerender/+Page.mdx | 12 ++++++++---- 3 files changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/pages/pre-rendering/+Page.mdx b/docs/pages/pre-rendering/+Page.mdx index 99170cb49d1..1de76ce2d55 100644 --- a/docs/pages/pre-rendering/+Page.mdx +++ b/docs/pages/pre-rendering/+Page.mdx @@ -83,7 +83,13 @@ The only difference between SSG and SSR is *when* the HTML is rendered: ## See also +Related docs: + +- - + +Pre-rendering options: + - - - diff --git a/docs/pages/pre-rendering/PreRenderDynamicRoutes.mdx b/docs/pages/pre-rendering/PreRenderDynamicRoutes.mdx index 24dbc6a6266..5f049197b95 100644 --- a/docs/pages/pre-rendering/PreRenderDynamicRoutes.mdx +++ b/docs/pages/pre-rendering/PreRenderDynamicRoutes.mdx @@ -1 +1 @@ -> Instead of providing a list of URLs, if you want a parameterized route to be resolved dynamically on the client-side, then see the workaround at [#1476 - Pre-rendered dynamic routes (static host deployment)](https://github.com/vikejs/vike/issues/1476). +> Instead of providing a list of URLs, if you want a parameterized route to be resolved dynamically on the client-side, see the workaround at [#1476 - Pre-rendered dynamic routes (static host deployment)](https://github.com/vikejs/vike/issues/1476). diff --git a/docs/pages/prerender/+Page.mdx b/docs/pages/prerender/+Page.mdx index 21e5755ba97..5afdab0fcd4 100644 --- a/docs/pages/prerender/+Page.mdx +++ b/docs/pages/prerender/+Page.mdx @@ -125,13 +125,17 @@ const onBeforePrerenderStart = someCondition() `boolean` (default: `false`) -Allow only some of our pages to be pre-rendered. +Allow only some of your pages to be pre-rendered. -This setting doesn't affect the pre-rendering process: it merely suppresses the warnings when some of our pages cannot be pre-rendered. +This setting doesn't affect the pre-rendering process: it merely suppresses the warning that some pages aren't pre-rendered. -> As explained in , if we don't pre-render all pages, then we need a production server. By using vite-plugin-vercel} href="/vercel#vite-plugin-vercel" />, we can still statically deploy our pre-rendered pages while using a production server for our non-pre-rendered pages. +> As explained in , if you don't pre-render *all* your pages then you need a production server. +> +> That said, if you cannot or don't want to pre-render all your pages while still deploying to a static host, then see the workaround at [#1476 - Pre-rendered dynamic routes (static host deployment)](https://github.com/vikejs/vike/issues/1476). +> +> Also, by using vite-plugin-vercel} href="/vercel#vite-plugin-vercel" />, you can statically deploy your pre-rendered pages while using a production server for your non-pre-rendered pages. -> Vike shows a warning that a page cannot be pre-rendered, when the page has a parameterized route (e.g. a `/movie/@movieId`, or a ), and there isn't any onBeforePrerenderStart() hook} href="/onBeforePrerenderStart" /> that provides at least one URL matching the page's route (e.g. `/movie/42`). +> Vike shows a warning that a page cannot be pre-rendered when the page has a parameterized route (e.g. a `/movie/@movieId`, or a ) while there isn't any onBeforePrerenderStart() hook} href="/onBeforePrerenderStart" /> that provides at least one URL matching the page's route (e.g. `/movie/42`). ### `noExtraDir`