The yeoman project encompasses a lot more. It's original design was very monolithic but the community and core team decided it's better broken into modules, so

The yeoman project encompasses a lot more. It's original design was very monolithic but the community and core team decided it's better broken into modules, so you primarily use much of yeoman through grunt, but much of that workflow is authored by the Yeoman dev team. There's yo (that scaffolds via generators), 10 officially supported generators that work with common webapps setups (e.g. angular backbone ember chrome-extension mocha karma), and (so far) 74 generators in the community building off this platform: https://npmjs.org/browse/depended/yeoman-generator https://npmjs.org/browse/depended/yeoman-generator Then other supplementary modules: grunt-contrib-compass, grunt-contrib-imagemin, grunt-contrib-htmlmin, grunt-contrib-livereload, grunt-regarde, grunt-svgmin, grunt-contrib-connect, grunt-bower-requirejs, grunt-usemin, node adapters for optipng and jpegtran, configstore. This grunt infrastructure designed and maintained by the project. In addition, the Yeoman also collaborates very heavily with the Bower and Grunt projects, both of which are accellerating very fast. There is considerable overlap in the core dev teams here, everyone working together amongst this disparate but congealing webapp developing tooling ecosystem.