Skip to content

Commit cabe649

Browse files
authored
docs: Improve "Thinking in React" for color-blind people (#3883)
1 parent 075b69c commit cabe649

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

content/docs/thinking-in-react.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ But how do you know what should be its own component? Use the same techniques fo
3939

4040
Since you're often displaying a JSON data model to a user, you'll find that if your model was built correctly, your UI (and therefore your component structure) will map nicely. That's because UI and data models tend to adhere to the same *information architecture*. Separate your UI into components, where each component matches one piece of your data model.
4141

42-
![Component diagram](../images/blog/thinking-in-react-components.png)
42+
![Diagram showing nesting of components](../images/blog/thinking-in-react-components.png)
4343

44-
You'll see here that we have five components in our app. We've italicized the data each component represents.
44+
You'll see here that we have five components in our app. We've italicized the data each component represents. The numbers in the image correspond to the numbers below.
4545

4646
1. **`FilterableProductTable` (orange):** contains the entirety of the example
4747
2. **`SearchBar` (blue):** receives all *user input*
Loading

0 commit comments

Comments
 (0)