This project is read-only.

Is it valid to organize features in single project like Orchard.Core ?

Topics: Customizing Orchard, Writing modules
Feb 6, 2015 at 7:53 AM
Edited Feb 6, 2015 at 7:58 AM
Looking in Orchard.Core project features are organized in there own folders with a manifest file (module.txt) , a and views folder.

Is it valid for us to use a similar approach in our own modules, to better organize structure.
So in 1 module have multiple folders each with there own manifest file , views folder and so on.
Are there any downsides to this ?
My impression is that Orchard finds the module.txt and considers its containing folder as an extension module.Correct?
Feb 7, 2015 at 7:55 AM
it's very tempting, right?
you could, but you would need to make a few small changes in orchard.framework.
However I personally against that approach. Because you might end up with a very big module which depends on each other.

Feb 7, 2015 at 10:54 AM
Edited Feb 7, 2015 at 10:56 AM
I agree, do it as long as you know what your doing.
Basically my views folder is getting quite messy so i would prefer to organize stuff in subfolders of my module.
what changes in orchard.framework are you referring to?
Thank you.