idiomatic Aurelia

**I'm submitting a feature request**

**Current behavior:**

While Aurelia tries to get out of your way, some of the concepts are "magical" to new frontend developers.

**Expected/desired behavior:**

* **What is the expected behavior?**
As part of the documentation it would be helpful to explain how you would do something without Aurelia, and then to show how Aurelia helps you do that.

* **What is the motivation / use case for changing the behavior?**
I have no idea if this course is free, https://egghead.io/lessons/javascript-redux-updating-the-state-with-the-fetched-data but it shows how you can write your own Redux implementation, and the reasoning behind the steps to get there.

I think this would also be useful for Aurelia.

Start by reviewing the existing Aurelia documentation and the linked Egghead Redux lesson for its explanation-first structure. Done means adding documentation that explains relevant concepts without Aurelia, then shows how Aurelia addresses them; the issue does not name specific files or tests.

Written by the indexing model from the issue text.