I’m new to Yeoman and I’m trying to figure out how to use it with backend scripts. I’m wondering about the best way to set up my project structure and workflow.
For a simple setup using jQuery and HTML5 Boilerplate with a PHP backend, I’m thinking of doing this:
Develop the frontend with Yeoman
Run yeoman build and use the dist folder for backend work
Copy dist to a public folder for backend adjustments
Repeat the process for any frontend changes
Is this approach effective? The Yeoman structure doesn’t quite match typical backend frameworks, and I’m curious if it’s possible to customize the folder names in Yeoman.
I’m also interested in tips for integrating Yeoman with frameworks like Angular or Ember when working with a backend. Any advice on creating a smooth workflow for both frontend and backend development would be much appreciated. Thanks!
Your approach sounds reasonable, but there are ways to streamline it further. Instead of copying the ‘dist’ folder manually, consider using Grunt or Gulp tasks to automate the process. These tools can watch for changes and automatically rebuild and copy files to your backend directory.
For integrating with frameworks like Angular or Ember, you might want to look into generator-angular or generator-ember, which are Yeoman generators specifically designed for these frameworks. They often include backend integration options out of the box.
As for customizing folder names, you can modify the Gruntfile.js or gulpfile.js in your Yeoman project to change output directories. This allows you to align Yeoman’s structure with your backend framework more closely.
Remember, Yeoman is highly customizable. You can create your own generator tailored to your specific stack if existing ones don’t quite fit your needs. This can greatly improve your workflow in the long run.
yo, ur approach is decent but theres room for improvement. maybe look into grunt or gulp for automating that copy process? theyd save u tons of time. also, check out specific generators for angular/ember if ur using those. they often have backend integration built-in. dont forget u can tweak yeomans config to match ur backend structure better!
hey, have u considered using a task runner like Gulp? it could make ur workflow smoother. also, what backend framework are u using? some frameworks have their own CLI tools that play nice with Yeoman. maybe we could brainstorm some ideas to integrate them better? what challenges have u faced so far with ur current setup?