We should separate chopsui elements into sets depending on how opinionated they are. 

For example, elements like chops-tree-status only really make sense in a specific use case whereas elements like chops-button are plain UI constructs that could be used in any service. Long-term, I want ChopsUI to be a mix of these kinds of elements with the plain UI elements generally being used as lower level components to create the mroe tailored elements. 

There are some open questions here:

- What should the categories be? 
- Should we consider making separate prefixes for elements in different categories? ie: similar to how Polymer's core elements have iron-* for lower level elements and paper-* for Material Design elements.