I'm a front-end developer to a couple of projects where I'm given a backend framework. Most of the time, I build on top of the Zend PHP framework. Because Zend already has a structure for it's file organization*, I'm wondering how Yeoman could fit in my workflow.
Is there now, or will there be, any ability to configure Yeoman to work inside a non-Yeoman directory structure? Unfortunately, I rarely have full control over a project (front and back-end) and have to work with other developers and their existing code base.
Much thanks for all of you guy's hard work to produce such a great product!
* Zend structure (partial example):
|------ scripts (contains the "root index" file)
|------ scripts (contains all view files, usually .phtml)
We are planning on making it more configurable yes.
This is great news that should benefit many like me that work with hybridized apps. Thanks for letting me know.
I vote for a Rails compatible generator. I use the Rails Asset pipeline and would like Yeoman to play nice with it.
@cerebralix I know this was a little while back, but have you checked out generator-angular-zend?
I just saw this now for the first time. This might actually be a case where assetgraph could be a relevant alternative, given its ability to find paths and dependencies by itself. Of course with the caveat that the urls have to be valid, but from the example file structure that seems likely