Describe challenges in working with the current Rave implementations:
- rave-jpa application context is responsible for more than JPA related configuration
- rave-commons has transitive dependencies to other rave projects
- template to page conversion happens in the repository
- shindig currently requires being run with unauthenticated requests
- widget repository needs getbycategory rather than using object reference
- properties organization is difficult to maintain
- more needs to be configurable through admin properties
- navigation elements are not dynamically driven
- css customization is not well understood
- application contexts are confusing at best