Re: Whats happening?

Lukas Renggli wrote: Ok... I am still stuggling to understand what this means. I thought that structures already have their own environments. Are you saying that a structure, having multiple documents, can have an environment as one of those. How will moving and copying work for these secondary-documents? How about a rule along the lines of "if I contain an 'environment' use it, otherwise use my parent's environment" ? I also think that you we need a different environment for editing environments. So can environments have environments? See below I am also attempting to make pier easier to use and harder to break. The scheme that I came up with looks like this. welcome admin user public site env sidebar header footer contents dev env boxes header contents Each of my top levels has different permissions. public and site are viewable by those that are not logged in. The user area requires the user to be logged in, and the admin and dev areas require you to be logged in as an admin-user. The dev hierarchy can only be edited by the superuser. User/public, use the site-env, and admin/dev/site use the dev-env. This allows the admin users to edit the site-env the environment of the overall site. While the admin and site areas themselves use the dev-env for display. This prevents admin users from breaking their working environment dev-env while changing the site-env. It works pretty well. I agree anything that help make things easy to use will be a good thing. I do not think that the current permissions model is flexible enough for any but the simpleset use cases. I think that if groups were to be able to have groups as members that might help. cheers Keith