Reading the Boilerplate

There's a ton to be learned from just reading and fiddling with the code that Yeoman generator-angular-fullstack produces. I have posted a repository with just that [boilerplate code here] (https://github.com/cofauver/boilerplate) and would encourage you to read through it. Even better would be to run the generator on your own system and read the code as you customize it. If you're curious which choices I made, here's my terminal dialog:

Having a working, readable piece of code that can easily livereload is a godsend. I can read through and understand what's going on piece by piece. I can manipulate pieces of code to see if I've understood their meanings. I can follow well-structured, well-organized code, that's written at a level higher than I am currently capable and attempt to emulate it in adding functionality. Unlike reading blogposts, browsing through StackOverflow, or following along with online lessons, you're in the driver's seat to engage directly with the code and find out how manipulating it could impact it's functionality.

Here are some aspects of the boilerplate that are well written and interesting to me:

##Fractal Hierarchy

The boilerplate is organized in a manner consistent with the current best practices for angular apps. Each feature is separated into all of the files that create it. Once you're looking at the code for login, you can see the html, the scss, and the javascript that makes login work. The model, view, and controller are all right there.

##Login