Best Practices for multiple authors using single project?

Question

We are having many issues, particularly with moving, renaming, and multiple check out warnings. We have a single project with many authors and it seems like RH is not designed to work that way. There is an article in the RH devnet-archive in an article entitled "Sharing RoboHelp Project Among Multiple Authors" that says"

"At first there may be the temptation to let every author work on every file in a project. This is certainly not a best practice. Regardless of source contraol, it is always best to designate certain authors as owning certain content-related sections, folders, or topics within a project -particulary at the folder level."

This statement, and our experience seems to indicate that RH is not a true CMS as we had envisioned. What are the best practices for this scenario to avoid stepping on each others toes and having problems with source control.

Peter Grainge · Answer

I have moved this to the source control forum for the gurus there to answer.

Meantime I must admit I read that statement the same way as you first time. However, on rereading I think what the author is saying is not that what you want cannot be done, rather it is best practice to guide authors to work in discrete areas.

I will leave it to the author or another guru to give you a more complete answer.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded