forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Koberg" <>
Subject RE: Link-Addressing, and breaking up the sitemap
Date Thu, 05 Sep 2002 10:07:24 GMT

> -----Original Message-----
> From: Marc Portier []

> Still: configuring the load of what forrest should know about
> your project all in *one* file seems logic to me.  (as long as it
> is all inside the one concern which I would largely define as
> "organize the project site" This would be involving: choosing
> some skin, and maybe setting some skin-specific customizations,
> decide on which parts get hooked up in which tabs, setup the
> libre auto-indexing rules, ...
> Even if the concerns would grow out of one role (person) this
> could still be the entry config-file that maybe lists where other
> files are.

I have found that two main config files are a good thing. One that describes the
site and one that describes the resources. The resources are referenced in the
site config for easy reuse.

I have some incomplete documentation with Relax NG Schemas (I think I generated
DTDs and W3 Schema) up at:


> whadayathink?
> using the CLI is about "staticalizing" your content.  The webapp
> does not have this concern, so only the CLI needs to be taking up
> this concern to 'relativise' all the /-leading references in the
> produced static content.
> (At first I mentioned some transformer for this, but 'in office'
> Steven correctly pointed out that this has only got to do with
> the use of the crawler.)

What happens when your static output is PDF or some other binary staticalized :)


View raw message