[opencms-dev] Best Practices for Settingup 'staging'environment for Content?

[Chirouze Olivier]

Hi Mathias and Shi,

Thanks for your comments. Mathias, you have perfectly understood my needs. What we would like to have is a module or any means to put comments on parts of a file, ideally dated and signed by the author of the comment, but only on the backend (the offline project). It's a workflow where authors can be multiple and need to collaborate before the file is actually published.

The published file is eventually a very basic html page without any commenting features... A basic monthly newsletter.

I won't have the time to investigate much more at the moment, but I will keep your suggestions in mind for later, Mathias.

Any other "full featured module" is also welcome!

Olivier

PS: very nice pictures Shi! :-)

> -----Original Message-----
> From: opencms-dev-bounces at opencms.org 
> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Mathias Lin
> Sent: 10 September 2008 08:13
> To: opencms-dev at opencms.org
> Subject: Re: [opencms-dev] Best Practices for Settingup 
> 'staging'environment for Content?
> 
> 
> Hi Shi,
> I think Olivier is looking for a commenting module for the 
> backend, where
> the validator can add notes to any kind of file (not just one certain
> filetype) for the editor to review. Something that integrates into the
> workplace.
> I think your module is meant more for frontend usage, right? 
> But can this
> functionality be integrated into the backend/workplace?
> Frontend commenting module has recently been published by 
> Alkacon, but it's
> also just for frontend usage from my understanding. 
> http://www.nabble.com/Alkacon-OAMP-Comments-module-available-t
d19197079.html
> Mathias
> 
> 
> 
> Shi Yusen wrote:
> > 
> > Something like this?
> > 
> http://www.cphoto.com.cn/cn/yingxiang/zhuanti/mlzgy308/mlzgzpz
> sy08.html
> > 
> > If so, we have such a commercial module. :)
> > 
> > Regards,
> > 
> > Shi Yusen/Beijing Langhua Ltd.
> > 
> > 
> > 在 2008-09-09二的 15:47 +0200，Chirouze Olivier写道：
> >> Thanks a lot for this information Mathias.
> >> 
> >> I will have a look at both soon.
> >> 
> >> By any chance, do you know any module that would allow users to set
> >> comments on files? (a "comment" field by file, or ideally, comments
> >> directly on the file, "a la Word")...
> >> 
> >> Thanks
> >> 
> >> Olivier
> >> 
> >> 
> >> > -----Original Message-----
> >> > From: opencms-dev-bounces at opencms.org 
> >> > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Mathias Lin
> >> > Sent: 09 September 2008 15:18
> >> > To: opencms-dev at opencms.org
> >> > Subject: Re: [opencms-dev] Best Practices for Setting up 
> >> > 'staging'environment for Content?
> >> > 
> >> > 
> >> > Hi Olivier,
> >> > 
> >> > yes, it's a missing feature. For very basic and quite static 
> >> > (fix rules)
> >> > workflow functionality we've extended the OpenCms (6.2.3) 
> >> > core class (mainly
> >> > CmsXmlContentEditor.java) and some workplace jsp files (edit.js,
> >> > editor_forms.jsp, editor_buttons.jsp under
> >> > /system/workplace/editors/xmlcontent/) - our approach:
> >> > We added a button into the editor's tool bar named 'save, 
> >> > notify and exit',
> >> > which looks up the 'responsible' group of the edited 
> file, and send a
> >> > notification mail with a link in it to the group members, so 
> >> > the validator
> >> > can go right to the editor screen to approve the content. A 
> >> > second publish
> >> > button also has the option to notify that the file has been 
> >> > approved and
> >> > published.
> >> > That would be the very basic approach.
> >> > 
> >> > 
> >> > For enhanced workflow, there exists a third-party module:
> >> > see 
> http://mail.opencms.org/pipermail/opencms-dev/2007q4/028561.html
> >> > and http://sourceforge.net/projects/bp-cms-commons/
> >> > 
> >> > 
> >> > Mathias
> >> > 
> >> > 
> >> > Chirouze Olivier wrote:
> >> > > 
> >> > > What is missing is the "go" on a file and some 
> >> > collaborative work tools:
> >> > > that would be great if "validators" could comment on 
> files and set a
> >> > > flag on them to make them ready to publish. If anyone can make
> >> > > suggestions?
> >> > > 
> >> > 
> >> > -- 
> >> > View this message in context: 
> >> > http://www.nabble.com/Re%3A-Best-Practices-for-Setting-up-%27s
> >> > taging%27-environment%09for-Content--tp19136042p19392198.html
> >> > Sent from the OpenCMS - Dev mailing list archive at Nabble.com.
> >> > 
> >> > 
> >> > _______________________________________________
> >> > This mail is sent to you from the opencms-dev mailing list
> >> > To change your list options, or to unsubscribe from the list, 
> >> > please visit
> >> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> >> > 
> >> 
> >> _______________________________________________
> >> This mail is sent to you from the opencms-dev mailing list
> >> To change your list options, or to unsubscribe from the 
> list, please
> >> visit
> >> http://lists.opencms.org/mailman/listinfo/opencms-dev
> > 
> > 
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the 
> list, please visit
> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> > 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/Re%3A-Best-Practices-for-Setting-up-%27s
taging%27-environment%09for-Content--tp19136042p19406940.html
> Sent from the OpenCMS - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, 
> please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>