Hi!
Robert Treat wrote:
>>>1) If all the static content (i.e. the content that does not change
>>>often) is stored in the database and is editable only through
>>>web-interface then there is a bottleneck: the person who
>>>gives access to web-interface. If the interface is not robust
>>>enough to let not-quite-trusted people use it, then the
>>>bottleneck is even more narrow. On the other hand, if the
>>>content is available in public CVS, then every one may check
>>>it out and edit it and later submit for inclusion.
>>
>>The same bottleneck applies either way as those with access to the admin
>>interface are basically those with cvs commit access. Still, CVS does
>>give more convenient read-only access than the web does.
>>
>
>
> I'd like to point out that from a management standpoint, I think we've
> been fairly responsive when it comes to news & events, so I don't see a
> bottleneck there. On top of that, ISTM that it is easier to for end
> users to submit news and to get it approved if its in a web/db based
> system.
I want to once again point out that this applied to static content, not
to news and events which should of course be managed through web interface.
