lukechilds
/
react.dev
mirror of https://github.com/lukechilds/react.dev.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2112 Commits
2 Branches
0 Tags
148 MiB
Tree: 55f37b4576
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '55f37b4576'
${ noResults }
react.dev/docs/01-why-react.md

30 lines
1.4 KiB
Raw Normal View History

move docs around, add likebutton
12 years ago
---
Remove numbers from URLs. This will let us keep docs in order on the filesystem but have reasonable permalinks. If we add something at 02- it doesn't result in lots of broken links.
12 years ago
id: why-react
move docs around, add likebutton
12 years ago
title: Why React?
Upgrade to Jekyll 3 Full list of changes is at https://jekyllrb.com/docs/upgrading/2-to-3/. The tl;dr of it is: - Relative permalinks were removed, so all the files in the `docs` subdirectory need their permalink to be prefixed with `docs/` - `post` and `page` types were renamed to `posts` and `pages` respectively - `jekyll-paginate`, `pygments` and `redcarpet` are all now optional, so I needed to explicitly add it to the Gemfile. Jekyll now uses `rouge` rather than `pygments` for syntax highlighting, but rouge does not support highlighting individual lines (`hl_lines`) so we need to continue using Pygments. - Layout metadata (eg. `sectionid`) is now on a `layout` variable rather than `page` Tested the following pages and confirmed that they all work: - "Docs" link (getting started page): http://127.0.0.1:4000/react/docs/getting-started.html - Downloads: http://127.0.0.1:4000/react/downloads.html - Tutorial: http://127.0.0.1:4000/react/docs/tutorial.html - A few pages under the "docs" subdirectory, to confirm they're working properly: - http://127.0.0.1:4000/react/docs/addons.html - http://127.0.0.1:4000/react/docs/why-react.html - http://127.0.0.1:4000/react/docs/create-fragment.html - A few tips: - http://127.0.0.1:4000/react/tips/false-in-jsx.html - http://127.0.0.1:4000/react/tips/style-props-value-px.html - Non-English versions of the page: - http://127.0.0.1:4000/react/docs/getting-started-it-IT.html - http://127.0.0.1:4000/react/docs/getting-started-ja-JP.html
9 years ago
permalink: docs/why-react.html
Remove numbers from URLs. This will let us keep docs in order on the filesystem but have reasonable permalinks. If we add something at 02- it doesn't result in lots of broken links.
12 years ago
next: displaying-data.html
move docs around, add likebutton
12 years ago
---
SSL/TLSize all the things! (convert http:// to https:// where appropriate) Update links to use https:// where it is supported. There's probably a lot more that could be fixed, but these are the core ones I found (especially the download links in order to prevent MITM attacks). Note that there are some fb.me links that will redirect to http:// even while accessed over https://, but this seemed like the best way to fix those for now. NOTE: Only non-third-party files were modified. There are references to http:// URLs in vendored/third-party files, but seems appropriate to fix upstream for those rather than editing the files. Also, copy one image locally to the blog, as it was hotlinking to a site that did not support https://. Last, use youtube-nocookie.com instead of youtube.com for video embeds, as the former doesn't try to set a cookie on load (privacy enhancement).
10 years ago
React is a JavaScript library for creating user interfaces by Facebook and Instagram. Many people choose to think of React as the **V** in **[MVC](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller)**.
First two sections of newdocs
12 years ago
remove two ideas from why react to add clarity
10 years ago
We built React to solve one problem: **building large applications with data that changes over time**.
First two sections of newdocs
12 years ago
More Uniform Formating Corrected so the formatting in this document matches the same as others.
10 years ago
## Simple
First two sections of newdocs
12 years ago
Tweaked the intro page Here are some ideas that I think work better: - 15 repetitions of "React". Removed a few. - The "two main ideas" weren't clearly separated. I put them under different headers and simplified the wording. - The "Give it Five Minutes section didn't sound as reassuring. Made it sound more certain.
12 years ago
Simply express how your app should look at any given point in time, and React will automatically manage all UI updates when your underlying data changes.
First two sections of newdocs
12 years ago
More Uniform Formating Corrected so the formatting in this document matches the same as others.
10 years ago
## Declarative
Tweaked the intro page Here are some ideas that I think work better: - 15 repetitions of "React". Removed a few. - The "two main ideas" weren't clearly separated. I put them under different headers and simplified the wording. - The "Give it Five Minutes section didn't sound as reassuring. Made it sound more certain.
12 years ago
When the data changes, React conceptually hits the "refresh" button, and knows to only update the changed parts.
First two sections of newdocs
12 years ago
Fix title casing and heading levels
12 years ago
## Build Composable Components
First two sections of newdocs
12 years ago
React is all about building reusable components. In fact, with React the *only* thing you do is build components. Since they're so encapsulated, components make code reuse, testing, and separation of concerns easy.
changing back to 'give it five minutes', tweak that sentence
12 years ago
## Give It Five Minutes
First two sections of newdocs
12 years ago
SSL/TLSize all the things! (convert http:// to https:// where appropriate) Update links to use https:// where it is supported. There's probably a lot more that could be fixed, but these are the core ones I found (especially the download links in order to prevent MITM attacks). Note that there are some fb.me links that will redirect to http:// even while accessed over https://, but this seemed like the best way to fix those for now. NOTE: Only non-third-party files were modified. There are references to http:// URLs in vendored/third-party files, but seems appropriate to fix upstream for those rather than editing the files. Also, copy one image locally to the blog, as it was hotlinking to a site that did not support https://. Last, use youtube-nocookie.com instead of youtube.com for video embeds, as the former doesn't try to set a cookie on load (privacy enhancement).
10 years ago
React challenges a lot of conventional wisdom, and at first glance some of the ideas may seem crazy. [Give it five minutes](https://signalvnoise.com/posts/3124-give-it-five-minutes) while reading this guide; those crazy ideas have worked for building thousands of components both inside and outside of Facebook and Instagram.
@vjeux comments
12 years ago
Fix title casing and heading levels
12 years ago
## Learn More
@vjeux comments
12 years ago
SSL/TLSize all the things! (convert http:// to https:// where appropriate) Update links to use https:// where it is supported. There's probably a lot more that could be fixed, but these are the core ones I found (especially the download links in order to prevent MITM attacks). Note that there are some fb.me links that will redirect to http:// even while accessed over https://, but this seemed like the best way to fix those for now. NOTE: Only non-third-party files were modified. There are references to http:// URLs in vendored/third-party files, but seems appropriate to fix upstream for those rather than editing the files. Also, copy one image locally to the blog, as it was hotlinking to a site that did not support https://. Last, use youtube-nocookie.com instead of youtube.com for video embeds, as the former doesn't try to set a cookie on load (privacy enhancement).
10 years ago
You can learn more about our motivations behind building React in [this blog post](/react/blog/2013/06/05/why-react.html).