[Flow] (Resources) Directory Structure per convention

[Christian Loock]

Hi,

I personally don't like the thought of being forced to have my public 
resources organized after any sort of convention that is not mine. I 
don't see any benefit in it. It will make you lose flexibility at least 
for having no gain. Having conventions is great and it is something that 
i really love about flow. But only when there is some gain through it. 
In this case I feel like it would only force you somewhere where you 
maybe don't want to go.


On 22.04.2014 15:44, Adrian Föder wrote:
> Hi,
>
> already quite a time ago, I remember some efforts to establish a 
> convention for a directory structure especially for resources, just 
> like "Public/JavaScripts" (i.e. plural) and /Styles (also plural, not 
> StyleSheets, etcpp)
>
> Is that settled somehow? I still think we should provide such a 
> convention.
>
>
> Besides, in my own project(s) I ended up with a Web/_Resources/Built 
> folder (made up by me, next to the existing /Static and /Persistent 
> folders).
>
> In this /Built folder, I put files which (per (my) convention) can 
> worriless be rebuilt from foreign sources like .scss oder .js.
>
> At the end, all of my .scss and .js files reside in my Package's 
> /Private folder and are built into 
> Web/_Resources/Built/[JavaScripts|Styles] on deployment.
>
> That's just a suggestion of mine, but as said: I find that quite handy 
> and once a directory convention is made, maybe this is worth being 
> considered.
>
> Best!
> Adrian
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow

-- 
Christian Loock
Web Developer
Renzel Agentur
www.renzel-agentur.de