Where I spend a couple hours learning that I don't know what I'm doing.
After my dive into the configuration files I felt like I had a pretty strong base to start from. I know what packages I'm using and what they do. I started by tweaking one end to end test to expect 'Small Catechism Flash Cards' as the header, compiled (missed that the e2e test script didn't compile automatically), ran the e2e test, and saw a failure. I then changed the Angular component, compiled, and ran the test and voila it passed. BDD at its finest! (Obviously my overconfidence was setting me up for failure.)
I thought, "Why not try to display a card, and so I don't get too far ahead, just the title of the card and what would be the front text." So I wrote a test that looked for 'The Ten Commandments' in an h1 and 'The Introduction' in an h2. The URL to access would have the form /set/1/1 (set for the resource /). I think I made a mistake in assuming this is how the card should be accessed in the application. It might make sense for an API to retrieve the card, but maybe not the way to do it for the UI, not sure yet.
The URL format lead me to investigate how to respond to the /set// URL. This lead me to routers. I looked at the book I'm working through and started to work off that example, but found that some of the components I was trying to import weren't there. I then found that the way routers are being handled has changed since rc0 (What? I thought API's were stablized at beta guess that was a bad assumption knowing that the Gmail was in public beta for 5 years). I tried to use the new route style, but kept getting a 404 when I tried to use them. I looked for a fix for a bit, but ended up assuming this was some bug since the documentation isn't complete I'm not betting the implementation is complete either. What I ended up doing was using 'router-deprecated' and using the examples from the book. After a few more missteps, and learning I needed to define a base href in my index.html I got a page up responding to /set/1/1, but not doing at all what I expected.
I looked at the example some more and I don't think this is the way I'm supposed to be writing the angular app or using routers. I'm going to pull back a little bit and study the philosophy of what makes a good Angular app, the proper use of components, and how to use routers.