nuxt
diff --git a/‎.github/ISSUE_TEMPLATE/bug-report-nuxt3.yml
Lines changed: 2 additions & 2 deletions b/‎.github/ISSUE_TEMPLATE/bug-report-nuxt3.yml
Lines changed: 2 additions & 2 deletions
diff --git a/‎.github/workflows/ci.yml
Lines changed: 9 additions & 8 deletions b/‎.github/workflows/ci.yml
Lines changed: 9 additions & 8 deletions
diff --git a/‎.github/workflows/docs.yml
Lines changed: 37 additions & 0 deletions b/‎.github/workflows/docs.yml
Lines changed: 37 additions & 0 deletions
diff --git a/‎docs/content/1.getting-started/3.bridge.md
Lines changed: 3 additions & 3 deletions b/‎docs/content/1.getting-started/3.bridge.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/content/1.getting-started/4.bridge-composition-api.md
Lines changed: 1 addition & 1 deletion b/‎docs/content/1.getting-started/4.bridge-composition-api.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/content/1.getting-started/6.migration.md
Lines changed: 5 additions & 7 deletions b/‎docs/content/1.getting-started/6.migration.md
Lines changed: 5 additions & 7 deletions
diff --git a/‎docs/content/2.concepts/1.introduction.md
Lines changed: 1 addition & 1 deletion b/‎docs/content/2.concepts/1.introduction.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/content/2.concepts/2.vuejs-development.md
Lines changed: 4 additions & 4 deletions b/‎docs/content/2.concepts/2.vuejs-development.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/content/2.concepts/3.rendering.md
Lines changed: 4 additions & 4 deletions b/‎docs/content/2.concepts/3.rendering.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/content/2.concepts/4.auto-imports.md
Lines changed: 9 additions & 5 deletions b/‎docs/content/2.concepts/4.auto-imports.md
Lines changed: 9 additions & 5 deletions
@@ -8,7 +8,8 @@ body:
         Please carefully read the contribution docs before creating a bug report
         👉 https://v3.nuxtjs.org/community/reporting-bugs
 
-        Please use the code sandbox template below to create a minimal reproduction
+        Please use a template below to create a minimal reproduction
+        👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
         👉 https://codesandbox.io/s/github/nuxt/starter/tree/v3-codesandbox
   - type: textarea
     id: bug-env
@@ -46,4 +47,3 @@ body:
       description: |
         Optional if provided reproduction. Please try not to insert an image but copy paste the log text.
       render: shell
-
@@ -2,9 +2,13 @@ name: CI
 
 on:
   push:
+    paths-ignore:
+      - 'docs/**'
     branches:
       - main
   pull_request:
+    paths-ignore:
+      - 'docs/**'
     branches:
       - main
 
@@ -57,9 +61,6 @@ jobs:
       - name: Lint
         run: yarn lint
 
-      - name: Lint (docs)
-        run: yarn lint:docs
-
   test-fixtures:
     runs-on: ${{ matrix.os }}
 
@@ -141,6 +142,11 @@ jobs:
         run: yarn test:types
 
   build-release:
+    if: |
+      github.event_name == 'push' &&
+      !contains(github.event.head_commit.message, '[skip-release]') &&
+      !contains(github.event.head_commit.message, 'chore') &&
+      !contains(github.event.head_commit.message, 'docs')
     needs:
       - lint
       - build
@@ -171,11 +177,6 @@ jobs:
           key: ${{ matrix.os }}-node-v${{ matrix.node }}-${{ github.sha }}
 
       - name: Release Edge
-        if: |
-          github.event_name == 'push' &&
-          !contains(github.event.head_commit.message, '[skip-release]') &&
-          !contains(github.event.head_commit.message, 'chore') &&
-          !contains(github.event.head_commit.message, 'docs')
         run: ./scripts/release-edge.sh
         env:
           NODE_AUTH_TOKEN: ${{secrets.NODE_AUTH_TOKEN}}
@@ -0,0 +1,37 @@
+name: Docs
+
+on:
+  push:
+    paths:
+      - 'docs/**'
+      - '.github/workflows/docs.yml'
+    branches:
+      - main
+  pull_request:
+    paths:
+      - 'docs/**'
+      - '.github/workflows/docs.yml'
+    branches:
+      - main
+
+jobs:
+  lint-docs:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node: [14]
+
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+          cache: 'yarn'
+
+      - name: Install dependencies
+        run: yarn --immutable
+
+      - name: Lint (docs)
+        run: yarn lint:docs
@@ -143,15 +143,15 @@ In case you need to extend options provided by `./.nuxt/tsconfig.json` further,
 
 ## Migrate Composition API
 
-If you were previously using `@vue/composition-api` or `@nuxtjs/composition-api`, please read the [composition api migration guide](/getting-started/bridge-composition-api).
+If you were using `@vue/composition-api` or `@nuxtjs/composition-api`, please read the [composition api migration guide](/getting-started/bridge-composition-api).
 
 ### Migrate from CommonJS to ESM
 
 Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/concepts/esm) for more info and upgrading.
 
 ## Remove incompatible and obsolete modules
 
-- Remove `@nuxt/content` (1.x). A rewrite for nuxt 3 is planned (2.x)
+- Remove `@nuxt/content` (1.x). A rewrite for Nuxt 3 is planned (2.x)
 - Remove `nuxt-vite`: Bridge enables same functionality
 - Remove `@nuxt/typescript-build`: Bridge enables same functionality
 - Remove `@nuxt/typescript-runtime` and `nuxt-ts`: Nuxt 2 has built-in runtime support
@@ -219,7 +219,7 @@ export default defineNuxtConfig({
 ```
 
 This `useMeta` composable uses `@vueuse/head` under the hood (rather than `vue-meta`) to manipulate your `<head>`.
-Accordingly, it is recommended not to use both the native Nuxt 2 `head()` properties as well as `useMeta`, as they may conflict.
+Accordingly, we recommend not to use both the native Nuxt 2 `head()` properties as well as `useMeta`, as they may conflict.
 
 For more information on how to use this composable, see [the docs](/docs/usage/meta-tags#usemeta-composable).
 
 
@@ -114,7 +114,7 @@ This function has been removed, but its use cases can be met by using `useNuxtAp
 
 These two functions have been replaced with a new composable that works very similarly under the hood: `useState`.
 
-The key differences are that you must provide a _key_ for this state (which previously will have been generated automatically for `ssrRef` and `shallowSsrRef`), and that it can only be called within a Nuxt 3 plugin (which is defined by `defineNuxtPlugin`) or a component instance. (In other words, you cannot use `useState` with a global/ambient context, because of the danger of shared state across requests.)
+The key differences are that you must provide a _key_ for this state (which Nuxt generated automatically for `ssrRef` and `shallowSsrRef`), and that it can only be called within a Nuxt 3 plugin (which is defined by `defineNuxtPlugin`) or a component instance. (In other words, you cannot use `useState` with a global/ambient context, because of the danger of shared state across requests.)
 
 ```diff
 - import { ssrRef } from '@nuxtjs/composition-api'
 
@@ -107,26 +107,24 @@ export default () => { }
 
 With Nuxt 3, Nuxt is now a build-time-only dependency, which means that modules shouldn't attempt to hook into the Nuxt runtime.
 
-Your module needs should work even if it's only added to [`buildModules`](/docs/directory-structure/nuxt.config#buildmodules) (instead of `modules`). For example:
+Your module should work even if it's only added to [`buildModules`](/docs/directory-structure/nuxt.config#buildmodules) (instead of `modules`). For example:
 
 - Avoid updating `process.env` within a Nuxt module and reading by a nuxt plugin; use [`runtimeConfig`](/docs/directory-structure/nuxt.config#publicruntimeconfig) instead.
 - (*) Avoid depending on runtime hooks like `vue-renderer:*` for production
 - (*) Avoid adding `serverMiddleware` by importing them inside the module. Instead, add them by referencing a file path so that they are independent of the module's context
 
 (*) Unless it is for `nuxt dev` purpose only and guarded with `if (nuxt.options.dev) { }`.
 
-### Add module meta
-
-Ensure your module is exporting meta object.
-
-\[TODO\]
+::alert{type=info icon=🔎}
+Continue reading about Nuxt 3 modules in the [Modules guide](/docs/advanced/modules).
+::
 
 ### Use TypeScript (optional)
 
 While it is not essential, most of the Nuxt ecosystem is shifting to use TypeScript, so it is highly recommended to consider migration.
 
 ::alert{icon=💡}
-You can start migration by simply renaming `.js` files, to `.ts`. TypeScript is designed to be progressive!
+You can start migration by renaming `.js` files, to `.ts`. TypeScript is designed to be progressive!
 ::
 
 ::alert{icon=💡}
 
@@ -16,7 +16,7 @@ To understand what is Nuxt, we need to understand what we need to create a moder
 
 This is only the tip of the iceberg, imagine having to set up all of this for your project, make it work, and then, maintain it over time. We have been doing this since October 2016, tuning all the configurations to provide the best optimization and performance for any Vue application.
 
-Nuxt takes care of all of this so you can focus on what matters: **creating your web application**.
+Nuxt takes care of this so you can focus on what matters: **creating your web application**.
 
 On top of this setup, Nuxt provides a [directory structure](/docs/directory-structure/app) to follow, focused on specific features to keep your focus on creating, not configuring.
 
 
@@ -21,7 +21,7 @@ Nuxt has always used Vue as a frontend framework. We chose to build Nuxt in top
 
 ### Components auto-imports
 
-Every Vue components created in the [`components/` directory](/docs/directory-structure/components) of a Nuxt project will be available in your project without having to import them. If a component is not used anywhere, it will not be included in your production’s code.
+Every Vue components created in the [`components/` directory](/docs/directory-structure/components) of a Nuxt project will be available in your project without having to import them. If a component is not used anywhere, your production’s code will not include it.
 
 ### Vue Router
 
@@ -39,7 +39,7 @@ Inside the `<template>` of the component, we use the `<Welcome>` component creat
 Try to replace the `<template>`’s content with a custom welcome message. The browser window on the right will automatically render the changes without reloading.
 
 ::alert{type="info"}
-💡 If you are familiar with Vue, you might wonder where is the `main.js` file that creates a Vue app. This part is done by Nuxt behind the scene.
+💡 If you are familiar with Vue, you might wonder where is the `main.js` file that creates a Vue app. Nuxt does this part behind the scene.
 ::
 
 **If you were a previous user of Nuxt 2 or Vue 2, keep reading to get a feel of the differences between Vue 2 and Vue 3, and how Nuxt integrates those evolutions.**
@@ -62,7 +62,7 @@ This results in faster first rendering (component creation) and updates, and les
 
 ### Smaller bundle
 
-With Vue 3 and Nuxt 3, a focus has been put on bundle size reduction. With version 3, most of Vue’s functionality, including template directives and built-in components are tree-shakeable. They will not be included in your production bundle if you don’t use them.
+With Vue 3 and Nuxt 3, a focus has been put on bundle size reduction. With version 3, most of Vue’s functionality, including template directives and built-in components are tree-shakeable. Your production bundle will not include them if you don’t use them.
 
 This way, a minimal Vue 3 application can be reduced to 12 kb gzipped.
 
@@ -105,7 +105,7 @@ The goal of Nuxt 3 is to provide a great developer experience around the composi
 
 ### Typescript support
 
-Both Vue 3 and Nuxt 3 have been written in Typescript. A fully typed codebase prevents mistakes and documents APIs usage. This doesn’t mean that you have to write your application in Typescript to take advantage of it. With Nuxt 3, you can opt-in by just renaming your file from `.js` to `.ts` , or add `<script lang="ts">` in a component.
+Both Vue 3 and Nuxt 3 are written in Typescript. A fully typed codebase prevents mistakes and documents APIs usage. This doesn’t mean that you have to write your application in Typescript to take advantage of it. With Nuxt 3, you can opt-in by renaming your file from `.js` to `.ts` , or add `<script lang="ts">` in a component.
 
 ::alert{type="info"}
 🔎 [Read the details about Typescript in Nuxt 3](/concepts/typescript)
 
@@ -14,23 +14,23 @@ While this technique allows building complex and dynamic UIs with smooth page tr
 ### Pros
 
 - **Development speed**: When working entirely on the client-side, we don't have to worry about the server compatibility of the code, for example, by using browser-only APIs like the `window` object.
-- **Cheaper:** Running a server adds a cost of infrastructure as you would need to run on a platform that supports Javascript. We can host Client-only applications on any static server, just with HTML, CSS, and Javascript files.
+- **Cheaper:** Running a server adds a cost of infrastructure as you would need to run on a platform that supports Javascript. We can host Client-only applications on any static server with HTML, CSS, and Javascript files.
 - **Offline:** Because code entirely runs in the browser, it can nicely keep working while the internet is unavailable.
 
 ### Cons
 
 - **Performance**: The user has to wait for the browser to download, parse and run javascript files. Depending on the network for the download part and the user's device for the parsing and execution, this can take some time and impact your user's experience.
-- **Search Engine Optimization**: Indexing and updating the content delivered via client-side rendering takes more time than an HTML document already built. This is related to the performance drawback we discussed, as search engine crawlers won't wait for the interface to be fully rendered in their first try to index the page. Therefore, your content will take more time to show and update in search results pages with pure client-side rendering.
+- **Search Engine Optimization**: Indexing and updating the content delivered via client-side rendering takes more time than an HTML document already built. This is related to the performance drawback we discussed, as search engine crawlers won't wait for the interface to be fully rendered in their first try to index the page. Your content will take more time to show and update in search results pages with pure client-side rendering.
 
 ### Examples
 
 Client-side rendering is a good choice for heavily interactive **web applications** that don't need indexing or frequently use the same users. It can leverage browser caching to skip the download phase on subsequent visits, such as **SaaS, back-office applications, or Online Games**.
 
 ## Universal Rendering
 
-When the browser requests a URL with universal (client-side + server-side) rendering enabled, a fully rendered HTML page is returned to the browser. Whether the page has been generated in advance and cached or is rendered on the fly, at some point, Nuxt has run the Javascript (Vue.js) code in a server environment, producing an HTML document. Users immediately get the content of our application, contrary to client-side rendering. This step is similar to traditional **server-side rendering** performed by PHP or Ruby applications.
+When the browser requests a URL with universal (client-side + server-side) rendering enabled, the server returns a fully rendered HTML page to the browser. Whether the page has been generated in advance and cached or is rendered on the fly, at some point, Nuxt has run the Javascript (Vue.js) code in a server environment, producing an HTML document. Users immediately get the content of our application, contrary to client-side rendering. This step is similar to traditional **server-side rendering** performed by PHP or Ruby applications.
 
-To not lose the benefits of the client-side rendering method, such as dynamic interfaces and pages transitions, the javascript code that runs on the Server is loaded by the client in the background once the HTML document has been downloaded. Once it is interpreted again by the browser (hence **Universal rendering**), Vue.js takes control of the document and enables interactivity.
+To not lose the benefits of the client-side rendering method, such as dynamic interfaces and pages transitions, the Client loads the javascript code that runs on the Server in the background once the HTML document has been downloaded. It is interpreted again by the browser (hence **Universal rendering**) and Vue.js takes control of the document and enables interactivity.
 
 Making a static page interactive in the browser is called "Hydration."
 
 
@@ -1,15 +1,19 @@
 # Auto imports
 
-Nuxt auto-imports helper functions, composables and Vue APIs to use across your application without explicitly importing them. Based on the directory structure, every Nuxt application can also use auto-imports for its own components, composables and plugins. These functions can be used in components, composables or plugins. However, auto imports don't currently work within the server scope. They just work within the Vue portion of your app.
+Nuxt auto-imports helper functions, composables and Vue APIs to use across your application without explicitly importing them. Based on the directory structure, every Nuxt application can also use auto-imports for its own components, composables and plugins. Components, composables or plugins can use these functions.
 
 Contrary to a classic global declaration, Nuxt preserves typings and IDEs completions and hints, and only includes what is actually used in your production code.
 
-::alert{type=info}
-💡 In the documentation, every function that is not explicitly imported is auto-imported by Nuxt and can be used as-is in your code.
+::alert{type=info icon=💡}
+In the documentation, every function that is not explicitly imported is auto-imported by Nuxt and can be used as-is in your code.
 ::
 
-::alert{type=info}
-🚧  We are working on a proper API reference that will include every Nuxt auto-imports. For now, you can find a reference on the framework repository: [github.com/nuxt/framework/blob/main/packages/nuxt3/src/auto-imports/imports.ts](https://github.com/nuxt/framework/blob/main/packages/nuxt3/src/auto-imports/imports.ts)  
+::alert{type=info icon=🚧}
+We are working on a proper API reference that will include every Nuxt auto-imports. For now, you can find a reference on the framework repository: [github.com/nuxt/framework/blob/main/packages/nuxt3/src/auto-imports/imports.ts](https://github.com/nuxt/framework/blob/main/packages/nuxt3/src/auto-imports/imports.ts)  
+::
+
+::alert{type=warning}
+Auto imports don't currently work within the [server directory](/docs/directory-structure/server).
 ::
 
 ## Nuxt auto-imports