From 4ad5c959ebf10c84e11b38d94d5da81c3cdff9d9 Mon Sep 17 00:00:00 2001 From: Daniel Roe Date: Fri, 10 Mar 2023 20:36:42 +0000 Subject: [PATCH] docs: remove reference to beta/rc/coming soon --- docs/2.guide/1.concepts/3.rendering.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/2.guide/1.concepts/3.rendering.md b/docs/2.guide/1.concepts/3.rendering.md index 68158d9bdc..e5a843e8e3 100644 --- a/docs/2.guide/1.concepts/3.rendering.md +++ b/docs/2.guide/1.concepts/3.rendering.md @@ -67,13 +67,13 @@ Client-side and universal rendering are different strategies to display an inter By default, Nuxt uses **universal rendering** to provide better user experience and performance, and to optimize search engine indexing, but you can switch rendering modes in [one line of configuration](/docs/api/configuration/nuxt-config#ssr). -## Coming in Nuxt 3 +## New Rendering Patterns in Nuxt 3 In most cases, universal rendering as performed in Nuxt 2 offers a good user and developer experience. However, Nuxt 3 takes universal rendering a step further by introducing hybrid rendering and edge-side rendering. ### Hybrid Rendering -Hybrid rendering allows different caching rules per route using **Route Rules** and decides how the Server should respond to a new request on a given URL. +Hybrid rendering allows different caching rules per route using **Route Rules** and decides how the server should respond to a new request on a given URL. ### Rendering on CDN Edge Workers @@ -87,7 +87,7 @@ Nitro is the new [server engine](/docs/guide/concepts/server-engine) that powers Previously every route/page of a Nuxt application and server must use the same rendering mode, client-side or universal. But in various cases, some pages could be generated at build time, while others should be client-side rendered. For example, think of a content website with an admin section. Every content page should be primarily static and generated once, but the admin section requires registration and behaves more like a dynamic application. -Nuxt 3 starting from rc.12 comes with the public beta for route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently Netlify and Vercel are supported). +Nuxt 3 includes route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently Netlify and Vercel are supported). - `redirect` - Define server-side redirects. - `ssr` - Disables server-side rendering for sections of your app and make them SPA-only with `ssr: false`