Remove unused functionality from the child template

We want to avoid providing a structure until we have some things
that really require overriding. Our most frequent reason for
child themes will be for style and Javascript, as well as custom
non-template functionality. We should setup this framework as such.
Add an example of a custom script enqueue
Merge pull request #2 from washingtonstateuniversity/child-framework

[PR] Alter the child theme starter to reflect the best case intent of child themes