- Why React?
- Intro and rundown
- Tooling and Setup
- React, all about components
- Creating our first component
- JSX, is what again?
- Loading CSS into react
- Application Layout
- Types of components
- Passing dynamic data into a component
- Prototype what what now ?
- What is State
- Stateless functional component
- Routing, getting around
- Working with React Events
- More Routing
- React immutability helpers
- Loading state with onClick
- Displaying state with JSX
- How do we update state?
- Issuses of state, it's complicated
- Redux, as a possible solution
- All the kids are doing it
- Project Page
- Declarative
- Component-Based
- Learn Once, Write Anywhere (loaded term)
- More Javascript than framework syntax
- Learning React is useful, even when moving to other frameworks
- Vue.js
- Angular
- Cycle.js
- Ember
- Course structure
- Excersises and setup files
- Building out a project, but please no more todo apps
- Tour of Heros
- It hits on a lot of good points, things used in everyday web app building.
- Display an array of things
- Hide or show items based on conditions
- Edit fields/properties of item in a collection
- Dashboard -> Master list -> detail view. Used all the time
- Added network calls from Github's API for real world experience
- Create React App
- ES2015 and lots of it
- Babel, transpiling
- Webpack & live reloading
- Lots of hidden configs, which is fine for now
- Eject app
*LINK
- Defined
The whole state of your app is stored in an object tree inside a single store. The only way to change the state tree is to emit an action, an object describing what happened. To specify how the actions transform the state tree, you write pure reducers.
- From the creator Tutorial