On Wed, May 30, 2012 at 10:25 AM, Jasha Joachimsthal <[email protected]> wrote: > On 30 May 2012 16:10, Sean Cooper <[email protected]> wrote: > >> Is anyone currently working on team pages, or working on defining a >> structure for it? >> >> I'd like to take a crack at defining it this week, but I don't want to >> interrupt anyone that might already be working on the problem. >> >> -Sean >> > > I am planning to work on it, but it's not clear yet when. So if you want to > start, go ahead :) What I need is a concept of a page that is shared with a > group of users, but the users cannot edit the page, only the administrator > of the page. See also [1]
I was looking through the code and saw what appears to be some additions into the main page controller for share pages... but that doesn't fully cover my use case. - same as yours but shared with everyone, not just a group of users. I think we should have a separate controller for these pages to keep the page controller as simple as possible. In my use cases I'm going to have a few hundred pages that everyone can read but only the administrator(s) will have access to update. I think we can recycle the methodology for sharing a page with a group of people that is used in the shared page model, but I'm going to have to add a flag for world-read-only instead of supplying a group for read access. If we build in the support for world-read-only then this would also cover the idea of public pages. > > [1] http://markmail.org/thread/5dfecb5gk7qynqdc > > Jasha
