why client and server separate folders in yo generator web apps

Supported Configurations

Client

  • Scripts: JavaScript, CoffeeScript, Babel
  • Markup: HTML, Jade
  • Stylesheets: CSS, Stylus, Sass, Less,
  • Angular Routers: ngRoute, ui-router

Server

  • Database: None, MongoDB
  • Authentication boilerplate: Yes, No
  • oAuth integrations: Facebook Twitter Google
  • Socket.io integration: Yes, No

What is Yoeman?? Why should we see this regularly in gruntfile.js?

Folks,

Any of you are aware of this yoeman? But sure, i am not in one of you. I frequently see in gruntfile.js having following code..

<%= yeoman.app %> & <%= yeoman.dist %>

In files..

js: {
files: [‘<%= yeoman.app %>/**/*.js’],
tasks: [‘newer:jshint:all’],
options: {

}
},
html: {
files: [‘<%= yeoman.app %>/**/*.html’],
options: {

}
},

I dont understand anything..coz i am new to all..neither grunt not yoeman.. i am a new born baby with no thoughts 😛

Lets meet yoeman 🙂

yoeman

Yoeman can write boilerplate code for your entire web application or individual pieces like Controllers and Models. Yeoman can fire up a preview web server and watch your files for edits in order to live reload changes and compile your Sass. Yeoman can also run your unit tests, minimize and concatenate your code, optimize images, plus more!

Yeoman also works with other tools for improving your productivity:

  • grunt is used to build, preview, and test your project, thanks to help from tasks curated by the Yeoman team and grunt-contrib.
  • gulp is an alternative to GruntJS that favors code over configuration.
  • bower is used for dependency management, so that you no longer have to manually download your front-end libraries.

You can install Yeoman generators using the npm command

Request to go thru this url once and even this

Stackoverflow says:

More specifically, yeah… Yeoman is a generator. For example, if I run the latest generator-angular, the Gruntfile.js it produces includes this bit of code:

yeoman: {
  // configurable paths
  app: require('./bower.json').appPath || 'app',
  dist: 'dist'
}

So you can see, at least from the generator I used, that <%= yeoman.app %> will default to a directory called ‘app’ and <%= yeoman.dist %> will point to ‘dist’. If I pasted the entire Gruntfile the generator created for me, you would also see these are used by many of the tasks that build and test the app.

Refer here

How to start up with yoeman?? here

Thought to explain the configuration and kickstart of yoeman..but after looking the documentation i changed my decision. Its really very simple with clear explanation & screen shots in the yoeman documentation

List of yoeman generators