A Padrino layer having opinionated decisions about the configuration of a large Padrino app based on multiple gems.
Convention over configuration AND opinionated decissions... as long as it restricts only the workflow for configuration of a "large SOA" style project, not the architecture and/or gems of the apps.
Maybe it will be liberating having some layout/config conventions to quickly test some ideas. Later more research could be done about what is needed for Padrino to implement the same thing in a more generic way.
- reserve the '/assets' path
- some "core" gem must exist when loading a gemified app