Edit Question - KnowledgeHub

Title Body

So, I've been anticipating Yeoman and it's already out for a week or so now. But after successfully installing it, I've been confused at the workflow and the implementation with backend script (API). Scenario 1 So let's say I don't need all those shiny BBB/Ember/Angular stuff and use Yeoman just for jQuery/H5BP/Modernizr backed with Codeigniter or Sinatra/Rails. Since yeoman server doesn't natively support PHP (I haven't tried Sinatra/Rails), I figure that the workflow is: Front End Development with Yeoman After it's finished, do yeoman build and then use the built dist folder as a base to develop backend (and probably copy the dist folder to another folder for backend implementation (let's say public folder) If I should change CSS/JS, use yeoman again, build and copy the dist folder to public again. So on and on... But using that workflow, that means the directory structure will be something like cool-app/ --app/ --yeoman development stuff --test/ --yeoman development stuff --dist/ --yeoman built stuff .dotfiles package.json Gruntfile.js It's nice and all, but quite a bit different with the CodeIgniter / Rails directory structure. Not to mention there are name difference ( is this configurable in Yeoman? ), so it's kinda hard to imagine a good workflow developing both Front End and Back End in one go, except using the built result as a base for the backend. Scenario 2 BBB/Ember/Angular. Frankly I've been just testing those stuff, so any tips to implement with backend code is welcome! Though for all I know, yeoman can generate the necessary files for those framework inside app folder, so I figure, the solution of the first scenario will kinda solve the problem for scenario 2

Tags (comma-separated) Cancel