> an actor mixin that adds a message handler often gets a gerund

So, what if we decide we want to make the ResourceManagementSettingKeys assembled in a handler chain fashion? Where each mixed-in trait defines all its own keys and adds them to the resourceManagementSettings val. That's the point I'd like to get to. The one thing I haven't figured out is how, in that case, I'd say `deploy-resources`, for example, depends on `deploy-stylesheets` and `deploy-scripts` if those two are defined in their respective traits...

Maybe Deploying extends something that can add keys to the settings and any keys added to it affect the dependencies of `deploy-*`?