What should it do?

In building a million admins, the biggest issues I've had is with displaying large lists, complex relationships, multiple views/states, and bulk editing/management.
### Features
- [ ] Navigation (base states)
- [ ] Breadcrumbs
- [ ] Tabbed views (nested states)
- [ ] Sortable, filterable list view with deep links
- [ ] Select2 integration
- [ ] Markdown conversation
- [ ] Bulk toggling of booleans (with _N of M_ totals in header)
- [ ] Pagination
### 3rd Party Libraries

Even though libraries like AngularUI help bootstrap/select2/markdown/etc. integration, the point is to see _how easy is it to integrate or leverage a 3rd party library with the codebase_.

Routing, however, is assumed to be a solved problem, and outside the scope of this project.

Of course, utility libraries like _underscore/lodash_ are expected to be used.
### Structure
- Folder/file structure should match a reasonable expectation for "bring your own convention" and not necessarily match starter kits or skeletons.
- The purpose isn't to prepare the app to be production-ready, but to exhibit how a knowledgeable developer would use the framework without necessarily knowing the "right way" (e.g. probably using `$scope.$watch` over a custom directive utilizing `ng-model`). This is debatable, as clarity of code and intent is better than crazy architecture.