"" wrote on 07/31/2009 06:46:39 AM:
> Author: Mark Turner
> I'm a
> literary editor, not a website designer, so I know little beyond the
> simple sites, which is precisely why Campsite seems so ideal for me,
> and the others in the group.
You may have found your perfect match indeed, as Campsite has primarily
focused on the ease of use for the editors and journalists from version
1.0 (in 2000) onwards. (One could say, that's why you have so many
webmasters on this list/forum asking basic questions
> I represent a writers' group who want to publish our own writing
> news newspaper, so Campsite seems ideal for that. The only hold-up
> is that some members want to be able to use the system to also
> publish their own little ezines on the same site.
> My question is whether it's possible to do this, and set up
> different distinct publications/ezines, where the staff/editor of
> one can't access the controls for any of the others. They want to
> be sure of their exclusive control over each of their own projects,
> without the worry of any new staff or group members in the future
> maybe turning out to be niusances.
Campsite does have a concept of multiple individual publications, so you
could easily create as many e-zines you want. BUT all staff users (campsite
distinguishes between staff and subscribers) have access rights to all
publications. In other words, the bad apples among your growing community
could do potential damage to other people's sites. But that's the end of
bad news.
Short of waiting for us to re-implement the sections-based permissions
(http://trac.campware.org/campsite/ticket/2662), which could be extended to
account for publications as well (will have to check on the status of that,
as we've postponed the implementation of the feature in May, so my memory
is not that fresh), there are several ways you could configure your main
magazine and the e-zines to avoid a tragedy of the commons of sorts.
For one, you'd could have separate installs of Campsite for the main
magazine and each new e-zine on your server, on different virtual hosts
(vhosts). Or make separate installs on different vhosts only for each
newbie (or let the newbies start with the blog via the blog plugin and then
"promote" or "demote" them based on behavior/merit). As with any
workaround, there are several inelegant consequences and a few unintended
benefits lurking around. Basically, such a setup would be harder to
maintain. The upside is that everyone gets to be king of his castle.
You could also consider playing with the configuration of individual user
rights, which are very granular in Campsite (e.g. certain people could
publish, but wouldn't be able to delete an article, or section, or
publication). The best way to get a quick idea of what's possible is to go
to the Campsite demo site (http://campsite-demo.campware.org/admin), log in
and go to Users/Staff/ and click on an existing user and then on "Click
here to customize user permissions" and see all the possible combinations.
The user interface of each user corresponds exactly to the permissions he
has (http://code.campware.org/manuals/campsite/3.3/index.php?id=21).
Ultimately, it all depends on your time frame for implementation and the
level of cooperation or separation that your group would like to have in
publishing.
Hope the above explanation makes things a bit clearer, and I apologize for
not making it more succinct.