I agree with PretzelFisch. It's not necessary to delve into framework minutia and ALL possible use cases in order to get a feel for how the frameworks operate.

I agree with PretzelFisch. It's not necessary to delve into framework minutia and ALL possible use cases in order to get a feel for how the frameworks operate. The OP made a very wise decision by choosing to build a demo app that incorporated a list and child components. Lists with child components provide a very succinct encapsulation of the primary challenges that JS frameworks must manage. Managing state between parent and child, one-way or two-way binding with repeatable items, etc.