A little better now. It is very important to understand how the flow
works and what the differen...

Closes #104.

This is to protect against minification. In that case it is possible to
end up with id collision...

Instead of moving whole configuration bit here I decided to mention
about the possibility of lin...

Closes #146.

Closes #143.

Just being consistent in naming.

Now it matches the content better and should be easier to approach.

Closes #136.

Header looks a bit better this way.

Appendices lose numbering... Better not to do that.
Frontmatter/mainmatter split seems to work t...

Related to #148.

Looks like this isn't needed anymore. `ecmaFeatures.modules = true` has
to be set to avoid `use ...

Closes #152.

Thanks @nii236!

Looks like this has changed at some point so better update it.

Related to
https://stackoverflow...

Make blockquote font color a bit darker

That didn't add much so removing.

Component design can get a chapter of its own. Now it just breaks the
flow.

Related to #109.

Mentioning about markup doesn't make sense given there isn't any.

Closes #141.

Now it fits the web and book layout better.

No need for this one as it doesn't add much to the whole.

There were a couple hanging around. It's better to generate these
dynamically when needed.

Fixed discovered linting errors while at it.

This bit became redundant given we solve it in the previous chapter. A
little lighter again.

This makes `react and flux` chapter a little lighter.

This can be added later in the chapter.

Otherwise dnd won't make sense.

This simplifies implementation somewhat. One less worry for dnd.

Still need to implement actual dnd algorithm.

Part of the discussion went away as the issues (ids etc.) have been
resolved earlier and won't b...

This will become an appendix. As a result the application gets styled in
Kanban chapter already....

Thanks to @agmcleod for sparring with me on this! That was very helpful.

It's a good idea to generate unique ids here already as it makes sense
to use them for keys inst...

This gets too complicated for my tastes. This might have to be split up
at least as a lot of thi...

This will avoid rework later and pays off in the next chapter.

This needs to be discussed earlier. Otherwise this single section will
require a huge number of ...

Better ux.

Now it's composite rule so it would be the first for sure. For some
reason just `.banner` didn't...

Make feedback banner fixed

Fix jsx require

Need to rethink the approach next and turn it into something index
based.

Still need to rework chapter 7 source partially to make this work
properly again. The idea is th...

Jumping straight to decorators instead. HOCs don't add much value here.

Now the solution relies on Alt utilities and scales far better. I expect
this will simplify late...

Good riddance. These will come back again in a separate chapter (after
linting).

The current solution isn't ideal as Alt isn't flexible enough yet.

Related: https://github.com/...

It is better to discuss Relay in another chapter. Just hurts the flow here.

Closes #103.

Now it's more to the point and hopefully easier to follow. This should
motivate the usage of Flu...

README rewrite

Update build_all.sh to include NPM dependencies

It defeats the purpose if an user needs to go to each project to install the dependencies. Usefu...

Add the section name when creating a new issue

Now initial data model goes to a section of its own. This should be a
little easier to follow.

Update path to bundle.js in 02_getting_started.md index.html file.

Correct formatting of JavaScript in introduction

Change Javascript to JavaScript to match formatting in the rest of the 00_introduction.md.

Improved chapter flow. It should be a little easier to follow now.

Better flow, removed some cruft.