Merge branch 'indonesian' of github.com:vuejs-id/docs-next into indonesian

Author: mandaputtra

.github/pull.yml

@@ -3,3 +3,13 @@ rules:
   - base: master
     upstream: vuejs:master # change `wei` to the owner of upstream repo
     mergeMethod: hardreset
+  - base: indonesian
+    upstream: master        # Required. Can be a branch in the same forked repo.
+    assignees:              # Optional
+      - mandaputtra
+    reviewers:              # Optional
+      - mandaputtra
+    conflictReviewers:      # Optional, on merge conflict assign a reviewer
+      - mandaputtra
+label: ":arrow_heading_down: pull"  # Optional
+conflictLabel: "merge-conflict"     # Optional, on merge conflict assign a custom label, Default: merge-conflict

src/.vuepress/config.js

@@ -344,7 +344,7 @@ module.exports = {
               },
               {
                 text: 'Vuex',
-                link: 'https://vuex.vuejs.org/'
+                link: 'https://next.vuex.vuejs.org/'
               },
               {
                 text: 'Vue CLI',

src/guide/migration/children.md

@@ -0,0 +1,38 @@
+---
+badges:
+  - removed
+---
+
+# $children <MigrationBadges :badges="$frontmatter.badges" />
+
+## Overview
+
+`$children` instance property removed from Vue 3.0 and no longer supported.
+
+## 2.x Syntax
+
+In 2.x, developers could access direct child components of the current instance with `this.$children`:
+
+```html
+<div ref="app" id="app">
+  <img alt="Vue logo" src="./assets/logo.png" width="25%" />
+  <my-button>Change logo</my-button>
+</div>
+```
+
+```js
+export default {
+  name: "App",
+  components: {
+    MyButton,
+  },
+  mounted() {
+    console.log(this.$children); // [VueComponent]
+  },
+};
+</script>
+```
+
+## 3.x Update
+
+In 3.x, `$children` property is removed and no longer supported. Instead, if you need to access a child component instance, we recommend using [$refs](/guide/component-template-refs.html#template-refs).

src/guide/migration/introduction.md

@@ -109,9 +109,10 @@ The following consists a list of breaking changes from 2.x:
 ### Removed APIs
 
 - [`keyCode` support as `v-on` modifiers](/guide/migration/keycode-modifiers.html)
-- [$on, $off and \$once instance methods](/guide/migration/events-api.html)
+- [$on, $off and $once instance methods](/guide/migration/events-api.html)
 - [Filters](/guide/migration/filters.html)
 - [Inline templates attributes](/guide/migration/inline-template-attribute.html)
+- [`$children` intance property](/guide/migration/children.md)
 - `$destroy` instance method. Users should no longer manually manage the lifecycle of individual Vue components.
 
 ## Supporting Libraries

src/guide/state-management.md

@@ -2,7 +2,7 @@
 
 ## Official Flux-Like Implementation
 
-Large applications can often grow in complexity, due to multiple pieces of state scattered across many components and the interactions between them. To solve this problem, Vue offers [vuex](https://github.com/vuejs/vuex), our own Elm-inspired state management library. It even integrates into [vue-devtools](https://github.com/vuejs/vue-devtools), providing zero-setup access to [time travel debugging](https://raw.githubusercontent.com/vuejs/vue-devtools/master/media/demo.gif).
+Large applications can often grow in complexity, due to multiple pieces of state scattered across many components and the interactions between them. To solve this problem, Vue offers [Vuex](https://next.vuex.vuejs.org/), our own Elm-inspired state management library. It even integrates into [vue-devtools](https://github.com/vuejs/vue-devtools), providing zero-setup access to [time travel debugging](https://raw.githubusercontent.com/vuejs/vue-devtools/master/media/demo.gif).
 
 ### Information for React Developers
 
@@ -118,4 +118,4 @@ You should never replace the original state object in your actions - the compone
 
 As we continue developing the convention, where components are never allowed to directly mutate state that belongs to a store but should instead dispatch events that notify the store to perform actions, we eventually arrive at the [Flux](https://facebook.github.io/flux/) architecture. The benefit of this convention is we can record all state mutations happening to the store and implement advanced debugging helpers such as mutation logs, snapshots, and history re-rolls / time travel.
 
-This brings us full circle back to [Vuex](https://github.com/vuejs/vuex), so if you've read this far it's probably time to try it out!
+This brings us full circle back to [Vuex](https://next.vuex.vuejs.org/), so if you've read this far it's probably time to try it out!

src/style-guide/README.md

@@ -1615,7 +1615,7 @@ app.component('TodoItem', {
 
 ### Non-flux state management <sup data-p="d">use with caution</sup>
 
-**[Vuex](https://github.com/vuejs/vuex) should be preferred for global state management, instead of `this.$root` or a global event bus.**
+**[Vuex](https://next.vuex.vuejs.org/) should be preferred for global state management, instead of `this.$root` or a global event bus.**
 
 Managing state on `this.$root` and/or using a global event bus can be convenient for very simple cases, but it is not appropriate for most applications.