Skip to content

Commit 4d5af05

Browse files
ktsnkazupon
authored andcommitted
docs: update outdated link and redirects (#1313)
* docs: update outdated guide of simple store pattern * docs: add redirect for old intro page
1 parent 12f6179 commit 4d5af05

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

docs/.vuepress/public/_redirects

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,21 @@
11
# redirect old urls to root
22

33
/en/api.html /api/
4+
/en/intro.html /en/guide/
45
/en/* /guide/:splat
56

67
/zh-cn/api.html /zh/api/
8+
/zh-cn/intro.html /zh/guide/
79
/zh-cn/* /zh/guide/:splat
810

911
/ja/api.html /ja/api/
12+
/ja/intro.html /ja/guide/
1013
/ja/* /ja/guide/:splat
1114

1215
/ru/api.html /ru/api/
16+
/ru/intro.html /ru/guide/
1317
/ru/* /ru/guide/:splat
1418

1519
/kr/api.html /kr/api/
20+
/kr/intro.html /kr/guide/
1621
/kr/* /kr/guide/:splat

docs/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,6 @@ This is the basic idea behind Vuex, inspired by [Flux](https://facebook.github.i
5858

5959
Although Vuex helps us deal with shared state management, it also comes with the cost of more concepts and boilerplate. It's a trade-off between short term and long term productivity.
6060

61-
If you've never built a large-scale SPA and jump right into Vuex, it may feel verbose and daunting. That's perfectly normal - if your app is simple, you will most likely be fine without Vuex. A simple [global event bus](https://vuejs.org/v2/guide/components.html#Non-Parent-Child-Communication) may be all you need. But if you are building a medium-to-large-scale SPA, chances are you have run into situations that make you think about how to better handle state outside of your Vue components, and Vuex will be the natural next step for you. There's a good quote from Dan Abramov, the author of Redux:
61+
If you've never built a large-scale SPA and jump right into Vuex, it may feel verbose and daunting. That's perfectly normal - if your app is simple, you will most likely be fine without Vuex. A simple [store pattern](https://vuejs.org/v2/guide/state-management.html#Simple-State-Management-from-Scratch) may be all you need. But if you are building a medium-to-large-scale SPA, chances are you have run into situations that make you think about how to better handle state outside of your Vue components, and Vuex will be the natural next step for you. There's a good quote from Dan Abramov, the author of Redux:
6262

6363
> Flux libraries are like glasses: you’ll know when you need them.

0 commit comments

Comments
 (0)