it helps some times What it really comes down to is what are you going to do when you update Framework\Control.php in Application XYZ. Are you going to go back to Application ABC and make that same change? What if it's a critical bug? For maintainability of all of your projects I'd go with your second option.
RESTFul Flat Hierarchy vs. Dynamic Hierarchy for Search Resource
around this issue Flat and hierarchical URIs could be both RESTful. The problem is elsewhere. Being RESTful suppose that URIs are identifiers of resources. What resource is identified by /wepapi/patients/0/studies/12/images? The images of studies 12.
this will help I was unable to find a way to organize the web parts into folders, so the best solution I found was to create a page for each step in hierarchy and finally one for the web part. First page had the following text: