Skip to content

Fix: flow.png in intro.md isn't responsive #793

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2017
Merged

Fix: flow.png in intro.md isn't responsive #793

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/en/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ It is a self-contained app with the following parts:
This is an extremely simple representation of the concept of "one-way data flow":

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

However, the simplicity quickly breaks down when we have **multiple components that share common state**:
Expand Down
2 changes: 1 addition & 1 deletion docs/fr/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ C'est une app auto-contenue avec les parties suivantes :
Voici une représentation extrèmement simple du concept de "one-way data flow" (_flux de données unidirectionnel_) :

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

Cependant, la simplicité s'évapore rapidement lorsque nous avons **de multiples composants qui partagent le même state** :
Expand Down
2 changes: 1 addition & 1 deletion docs/ja/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ new Vue({
これらは"単方向データフロー"のコンセプトの極めてシンプルな責務です:

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

しかし、単純さは、**共通の状態を共有する複数のコンポーネントを持ったときに**、すぐに破綻します:
Expand Down
2 changes: 1 addition & 1 deletion docs/kr/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ new Vue({
이것은 "단방향 데이터 흐름" 개념의 매우 단순한 도표입니다.

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

그러나 **공통의 상태를 공유하는 여러 컴포넌트** 가 있는 경우 단순함이 빠르게 저하됩니다.
Expand Down
2 changes: 1 addition & 1 deletion docs/ru/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ new Vue({
Вот простейшее представление концепции "однонаправленного потока данных":

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

Простота, к сожалению, быстро исчезает при появлении **нескольких компонентов, основывающихся на одном и том же состоянии**, когда:
Expand Down
2 changes: 1 addition & 1 deletion docs/zh-cn/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ new Vue({
以下是一个表示“单向数据流”理念的极简示意：

<p style="text-align: center; margin: 2em">
<img style="max-width:450px;" src="./images/flow.png">
<img style="width:100%;max-width:450px;" src="./images/flow.png">
</p>

但是，当我们的应用遇到**多个组件共享状态**时，单向数据流的简洁性很容易被破坏：
Expand Down