forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Jose Pablos <>
Subject Re: Cleaning Forrest source directory madness
Date Fri, 13 Jun 2003 12:32:12 GMT

> Juan Jose, what you ask is exactly what I have been asking to have since 
> some months now. But some developers feel that for the it's better to 
> divide content in directories.

would you mind pointing to that discussion?, I could not find it on the 
mailing list.
Is performance the main reason?

> My proposal is made to try and take care of both uses, so that you can 
> decide to divide by directories or keep all together.

Well, I am not sure about which uses do you refer. I would like to see 
this to be real:

Easy and simple, the second point talks about edit presentation-neutral 
content, so only the content that is presentation neutral should go to 
the content directory.

I would define content images in cases similiar to this one :

/about/logo.xml with a <img src="images/logo.png"/>

Mainly because you talk about the logo itself. But if you have <img 
src="images/logo.png"/> in all the pages then it belongs to the skin 
unless you only talk about the logo in your site :-)

Before we add images to the content directory we need to ask ourselves 
if there are really content or if belongs really to the presentation layer.

Maybe this problem raise because we have not got a way to customize the 
skin or look and feel based on the resource ie.:  /parnerts/*. that 
would be a diferent issue.

But as we say on the site. By separating content from presentation makes 
things easier.



View raw message