suggestion: split chapter examples in repo into sections

[tomByrer]

This way, someone may know if their code matches what you actually have mid way in the chapter. example folder structure

• 02_developing_with_webpack/kanban_app
  • a_setting-up-assets
  • b_splitting-up-the-configuration
  • (even more changes...)

[bebraw]

The restructuring effort is going to help with this a bit. There are more chapters so you get more milestones to compare against. It's still missing numbering, though, but that will be added soon.

I'm not so sure of adding more granularity just yet. The problem is that if I change something early on, the change will cascade through each single step. I would need an automatic way to manage these kind of updates to keep this maintainable.

My current thinking is that the most sensible option would be to solve this through scripting. We could have a script that would go through the chapter code diffs and then write a repository based on that. Each step could become a git commit even. Automating it this way would solve a major pain point for me although this won't be trivial to pull off.

Let's leave this issue open as that's one of those things I want to tackle.

[bebraw]

As an intermediate solution I've split up the dev version into separate parts and smaller chapters. This gives you more checkpoints you can refer to. I feel this is a good compromise and worth doing anyway.