forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject [VOTE] Sitemap user visibility and scope in Forrest
Date Tue, 15 Apr 2003 07:22:27 GMT

The last discussion on nuggets has shown that there are two possible 
roads that Forrest can take.

(a) Make the sitemap a central concept to Forrest, as it is for Cocoon.
    Encourage users to edit the sitemap to change the structure of their

(b) Hide the sitemap, and add intermediate layers that provide a 'user
    friendly' interface to structural concerns.

Till now, we have mainly gone the route of (a), by creating mechanisms 
to keep the sitemap away from users. This makes it easier for them, and 
most important makes Forrest easily upgradeable. If users touch the 
sitemap, they will have to reedit the one of the new Forrest, going out 
of synch and possibly not upgrading Forrest because of it. I don't want 
that to happen.

Thus, I ask to vote on this.

Should Forrest pursue the goal of "hiding" the sitemap as in case (a)?
This does not block users to do it, just ensures that we don't *require* 
it to happen.


Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

View raw message