From 72c9f2a4475f99623d45422b5e44408a6d1ed47e Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Thu, 4 May 2017 12:42:13 +0200 Subject: [PATCH 1/5] Add french translation link Signed-off-by: Bruno Lesieur --- themes/vue/layout/partials/language_dropdown.ejs | 1 + 1 file changed, 1 insertion(+) diff --git a/themes/vue/layout/partials/language_dropdown.ejs b/themes/vue/layout/partials/language_dropdown.ejs index dcebf0f71f..94aa4f69a8 100644 --- a/themes/vue/layout/partials/language_dropdown.ejs +++ b/themes/vue/layout/partials/language_dropdown.ejs @@ -6,5 +6,6 @@
  • Русский
  • 한국어
  • Português
    • +
  • Français
    • From e4a1fbd64b543551241c8fc7c5f51d85b162f118 Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Thu, 11 May 2017 11:57:12 +0200 Subject: [PATCH 2/5] kebab-case explaination updates Signed-off-by: Bruno Lesieur --- src/v2/guide/components.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/v2/guide/components.md b/src/v2/guide/components.md index 841eee6f98..309913193a 100644 --- a/src/v2/guide/components.md +++ b/src/v2/guide/components.md @@ -1155,7 +1155,7 @@ When using _string_ templates however, we're not bound by HTML's case-insensitiv - kebab-case - camelCase or kebab-case if the component has been defined using camelCase -- kebab-case, camelCase or Title case if the component has been defined using TitleCase +- kebab-case, camelCase or TitleCase if the component has been defined using TitleCase ``` js components: { @@ -1166,14 +1166,14 @@ components: { ``` ``` html - + - - + + - - - + + + ``` This means that the TitleCase is the most universal _declaration convention_ and kebab-case is the most universal _usage convention_. @@ -1181,7 +1181,7 @@ This means that the TitleCase is the most universal _declaration convention_ and If your component isn't passed content via `slot` elements, you can even make it self-closing with a `/` after the name: ``` html - + ``` Again, this _only_ works within string templates, as self-closing custom elements are not valid HTML and your browser's native parser will not understand them. From 20d0d4e1fe544fa3d3eef9803af5c8735ae12835 Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Thu, 11 May 2017 11:59:27 +0200 Subject: [PATCH 3/5] kebab-case to kebab-cased Signed-off-by: Bruno Lesieur --- src/v2/guide/components.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/v2/guide/components.md b/src/v2/guide/components.md index 309913193a..36e59f73f0 100644 --- a/src/v2/guide/components.md +++ b/src/v2/guide/components.md @@ -1159,21 +1159,21 @@ When using _string_ templates however, we're not bound by HTML's case-insensitiv ``` js components: { - 'kebab-case-component': { /* ... */ }, - camelCaseComponent: { /* ... */ }, - TitleCaseComponent: { /* ... */ } + 'kebab-cased-component': { /* ... */ }, + camelCasedComponent: { /* ... */ }, + TitleCasedComponent: { /* ... */ } } ``` ``` html - - + + - - - + + + ``` This means that the TitleCase is the most universal _declaration convention_ and kebab-case is the most universal _usage convention_. From 91befe80f301f082bdbe3aa7b9f92f8254aaed3f Mon Sep 17 00:00:00 2001 From: Chris Fritz Date: Thu, 18 May 2017 20:46:55 -0400 Subject: [PATCH 4/5] Remove space before self-closing component --- src/v2/guide/components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/components.md b/src/v2/guide/components.md index 36e59f73f0..c544bbfdaa 100644 --- a/src/v2/guide/components.md +++ b/src/v2/guide/components.md @@ -1181,7 +1181,7 @@ This means that the TitleCase is the most universal _declaration convention_ and If your component isn't passed content via `slot` elements, you can even make it self-closing with a `/` after the name: ``` html - + ``` Again, this _only_ works within string templates, as self-closing custom elements are not valid HTML and your browser's native parser will not understand them. From 40e296e918fe8fbbfbd6065589c75f7a304300fe Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Mon, 3 Jul 2017 16:59:24 +0200 Subject: [PATCH 5/5] Replace NPM by npm same as official documentation Signed-off-by: Bruno Lesieur --- src/v2/guide/installation.md | 6 +++--- src/v2/guide/migration.md | 2 +- src/v2/guide/single-file-components.md | 2 +- src/v2/guide/typescript.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/v2/guide/installation.md b/src/v2/guide/installation.md index 2af3bf66e4..23a7bea361 100644 --- a/src/v2/guide/installation.md +++ b/src/v2/guide/installation.md @@ -35,9 +35,9 @@ Recommended: [https://unpkg.com/vue](https://unpkg.com/vue), which will reflect Also available on [jsDelivr](//cdn.jsdelivr.net/vue/latest/vue.js) or [cdnjs](//cdnjs.cloudflare.com/ajax/libs/vue/{{vue_version}}/vue.js), but these two services take some time to sync so the latest release may not be available yet. -## NPM +## npm -NPM is the recommended installation method when building large scale applications with Vue. It pairs nicely with module bundlers such as [Webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/). Vue also provides accompanying tools for authoring [Single File Components](single-file-components.html). +npm is the recommended installation method when building large scale applications with Vue. It pairs nicely with module bundlers such as [Webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/). Vue also provides accompanying tools for authoring [Single File Components](single-file-components.html). ``` bash # latest stable @@ -63,7 +63,7 @@ $ npm run dev ## Explanation of Different Builds -In the [`dist/` directory of the NPM package](https://unpkg.com/vue@latest/dist/) you will find many different builds of Vue.js. Here's an overview of the difference between them: +In the [`dist/` directory of the npm package](https://unpkg.com/vue@latest/dist/) you will find many different builds of Vue.js. Here's an overview of the difference between them: | | UMD | CommonJS | ES Module | | --- | --- | --- | --- | diff --git a/src/v2/guide/migration.md b/src/v2/guide/migration.md index 06f81f4f8a..bf8365f4ab 100644 --- a/src/v2/guide/migration.md +++ b/src/v2/guide/migration.md @@ -1052,7 +1052,7 @@ text.toLowerCase() #### Replacing the `pluralize` Filter -The [pluralize](https://www.npmjs.com/package/pluralize) package on NPM serves this purpose nicely, but if you only want to pluralize a specific word or want to have special output for cases like `0`, then you can also easily define your own pluralize functions. For example: +The [pluralize](https://www.npmjs.com/package/pluralize) package on npm serves this purpose nicely, but if you only want to pluralize a specific word or want to have special output for cases like `0`, then you can also easily define your own pluralize functions. For example: ``` js function pluralizeKnife (count) { diff --git a/src/v2/guide/single-file-components.md b/src/v2/guide/single-file-components.md index 0ab7995e3b..f04619bc20 100644 --- a/src/v2/guide/single-file-components.md +++ b/src/v2/guide/single-file-components.md @@ -54,7 +54,7 @@ Even if you don't like the idea of Single-File Components, you can still leverag With `.vue` components, we're entering the realm of advanced JavaScript applications. That means learning to use a few additional tools if you haven't already: -- **Node Package Manager (NPM)**: Read the [Getting Started guide](https://docs.npmjs.com/getting-started/what-is-npm) through section _10: Uninstalling global packages_. +- **Node Package Manager (npm)**: Read the [Getting Started guide](https://docs.npmjs.com/getting-started/what-is-npm) through section _10: Uninstalling global packages_. - **Modern JavaScript with ES2015/16**: Read through Babel's [Learn ES2015 guide](https://babeljs.io/docs/learn-es2015/). You don't have to memorize every feature right now, but keep this page as a reference you can come back to. diff --git a/src/v2/guide/typescript.md b/src/v2/guide/typescript.md index 7e0d378353..4b459fa1fb 100644 --- a/src/v2/guide/typescript.md +++ b/src/v2/guide/typescript.md @@ -10,11 +10,11 @@ In Vue 2.2 we introduced dist files exposed as ES modules, which will be used by We plan to move all official declarations to use ES-style exports in the future. Please see [Recommended Configuration](#Recommended-Configuration) below on a future-proof setup. -## Official Declaration in NPM Packages +## Official Declaration in npm Packages A static type system can help prevent many potential runtime errors, especially as applications grow. That's why Vue ships with [official type declarations](https://github.com/vuejs/vue/tree/dev/types) for [TypeScript](https://www.typescriptlang.org/) - not only in Vue core, but also for [vue-router](https://github.com/vuejs/vue-router/tree/dev/types) and [vuex](https://github.com/vuejs/vuex/tree/dev/types) as well. -Since these are [published on NPM](https://unpkg.com/vue/types/), and the latest TypeScript knows how to resolve type declarations in NPM packages, this means when installed via NPM, you don't need any additional tooling to use TypeScript with Vue. +Since these are [published on npm](https://unpkg.com/vue/types/), and the latest TypeScript knows how to resolve type declarations in npm packages, this means when installed via npm, you don't need any additional tooling to use TypeScript with Vue. ## Recommended Configuration