• Build familiarity with Redux's API
• Use Redux advanced features to solve common patterns in state management

Before reading the Introduction, try to write down your answers to the following questions. As you read, see whether your answers match up to the documentation.

• Why do people use Redux? What problems does it solve?
• List the core concepts of redux. What role do each of them play?
• What are the principles of developing using Redux?

Read the Motivation, Core Concepts, and Three Principles sections from the Introduction. Together, they should take about 10 minutes.

After reading the introduction sections, answer the following questions.

• What surprised you as you were reading the docs? What was new to you?
• Revisit your pre-check answers. What changes you would make now that you have read the Introduction?

Follow the steps in the Basic Tutorial to reproduce a TodoList app. This tutorial will take about 20 minutes to complete.

Follow the steps in the Advanced Tutorial to build an app with async actions and middleware. This tutorial will take about 30 minutes. Be sure to get the code to run at each intermediate step. Get the Reddit API example running. Read through the working code, and see if you can explain each line. If there's a line that you don't understand, treat that like a bug. Use the tutorial, google, or work with a colleague to help make sure you have an understanding of what each line of code is doing.

There are a lot of links out to further reading about Redux. The Recipes are interesting to browse, because they present solutions to scenarios that developers frequently face.

From the Recipes, you should read Configuring Your Store, Using the Object Spread Operator, Reducing Boilerplate, Writing Tests, Computing Derived Data, Implementing Undo History, and the 12 pages on Structuring Reducers. Read each of the recipes and run all of the code snippets in each one.

Reading and running the examples from all 18 Recipes pages will take about an hour.

The Redux FAQ answers a ton of commonly asked questions about redux.

Read the 50 or so questions in the index. Before clicking through to the responses in the documentation, write down your best answer to all of the questions. Next, read the answers provided by the documentation. How well did your answers match up? Which areas are still confusing to you?

Answering the FAQ questions yourself, then reading and checking your answers against those in the documentation will take about an hour.