[Yanel-dev] organization of data

[Josias Thöny]

Evaldas Taroza wrote:
> Hi,
> Maybe we should think about how to better organize data in the 
> repository. I mean we need some conventions. Currently we just put 
> everything into /data and that's it. So javascripts, xslt, jelly, css 
> together with the actual content gets there. I don't think it is nice. 
> Because some of the scripts (like jelly, xslt) belong to some of the 
> content and is not reusable, so they should lie somewhere logically 
> close to each other.

I see your point but I think there are always different ways to group 
things.
In one of our projects most of the js/xslt/css/img is reused between 
different resource types/usecases, and only the jelly is completely 
specific. In this case I don't know if it makes sense to group the 
different files according to resource type.

Anyway, if you think the reorganization is useful for you, feel free to 
do it.

Maybe something related:
Would it make sense to split the repo content into actual user-editable 
content and application-specific stuff?
Let's say we add two folders to the repository:
/content/
/app/
Now all the xslt/jelly/js/css goes somewhere into /app/ and the 
user-editable content goes into /content/

This would simplify upgrades of an installation where one needs to 
upgrade e.g. some xslt but wants to keep the content which was created 
by the users.

I know in some projects the application files like xslt or css may be 
editable for users. In this case this separation doesn't make much 
sense, but on the other hand many projects don't allow users to edit xslt.

Or should we use two separate repositories?

I'm not sure if this is a good solution but I consider the current mix a 
real problem for upgrading.

WDYT?

josias

> 
> I saw Josias is using some layout according to usecases.
> 
> Has anyone suggestions about the conventions?
> 
> Evaldas
> 


-- 
Josias Thöny
Wyona - Open Source Content Management
http://www.wyona.com