I have to say that Joomla does this very nicely. Now, I hate to be one to call out another CMS as an example ("Well, if you were just more like..." is not my intention). They have their drawbacks, and learning from their strengths is a good thing.
Every piece of Dolphin code, every module, every add-on should have two parts. The part that gets installed in the directory where it needs to be to function as a part of Dolphin, and the part that gets dropped into /templates/[active-template-directory]/module-name.css.
Even see more Joomla does not force these standards, causing a lot of cleaning up on CSS code whenever a new module is installed, either because of css files being spread all over or because of inline (throws up a bit in the back of my throat) styling added into the code itself, rather than a standalone CSS sheet. *cries*
To make it two-part like this as a standard would allow some pretty amazing things, design-wise, and be amazing for Dolphin, IMHO.
Honestly, I think that the first thing that will do a Dolphin site owner is to customize his site's look (the only thing that many of BoonEx "customers" will ever do)....
To split a module in 2 folders, one for the functionality and another one for the template, will be very easy to do for a developer.
Having to search and edit dozens of template files will be very difficult for most of site owners who will just customize his/her site...
I think that this is a very good see more idea to regroup all the files of a functionality in a module folder. Why this same idea (to regroup all styles files in a template folder ) will be wrong for the template ???
If it were some technical problem this will be a good reason... but there is none... at least none that I can see...
I call such things BoonEx syndrome: flying to high, searching to far... when the best solution is just under the shoes :-))
Every piece of Dolphin code, every module, every add-on should have two parts. The part that gets installed in the directory where it needs to be to function as a part of Dolphin, and the part that gets dropped into /templates/[active-template-directory]/module-name.css.
Even see more
Hope that BoonEx will consider our point of view...
To split a module in 2 folders, one for the functionality and another one for the template, will be very easy to do for a developer.
Having to search and edit dozens of template files will be very difficult for most of site owners who will just customize his/her site...
I think that this is a very good see more