Authoring - Cloning projects

You can clone an entire project with files, snippets, object names and pointers included. The next example demonstrates how to clone the entire 'Animals - Information' project.

Copying a project folder

Popup the menu of the folder and select 'Copy'.

Pasting the project folder as a clone

Paste at the required position in the Workbench tree.

Cloning the project

Set the cloning options on the 'Generate clone' window and click 'Start'. The entire folder along with the gallery is scanned. This can take awhile and can be resource consuming.In case your Workbench would run into memory problems consider changing the Workbench memory settings.

Objects directly shared outside the scope of the clone.


We advise you to read How shares and hyperlinks are treated in a clone to understand the usage of these objects.


Remain shared.


If you choose this option then the shared objects that occur in a folder outside the clone scope are not cloned. In other words, those shares remain intact which is in common cases the most obvious choice.


Are cloned.


If you select this option then the shared objects that occur in a folder outside the clone scope are cloned, meaning the shared object becomes a new instance and looses its shared behavior in the clone. Use this options to create a full clone with new object instances.

In any case, shared objects that are contained in the clone scope are cloned but they retain their share behavior in the clone result.

Also hyperlinks are involved. If a hyperlink points to a shared object outside the scope of the clone, then with the option 'Remain shared' the hyperlinks in the cloned result will still point to their original object. With the option 'Are cloned' the hyperlinks in the cloned result will point to their cloned instance.

Also clone.


Annotations, Feedback.


Select these options to include the associated annotations and/or feedback in the clone result.


Project files, Snippets.


These options apply to the files and/or the snippets of the project gallery (or galleries) in case the folder to be cloned is a project folder or in case it holds one or more dependent project folders.

If you switch off this (these) option(s) then the files and/or snippets in the clone result are shared with the original project(s).

If you switch on this (these) option(s) then the files and/or snippets are cloned. However, files and snippets can be directly shared in other projects. In that case the option 'Remain shared/Are cloned' determines whether the shared files and/or snippets will be actually cloned or not.


Scanning the folder and the gallery

As soon as the folder is scanned a window will prompt you to specify a new project name for the clone.

Assigning a new project name

Should there be additional projects in the folder's dependants then this window will list you all the involved project names. You will have to specify a new name for each of them. If you cannot assign all the new project names, the clone process will stop. You can always rename the cloned project afterwards.

A project folder and its gallery cloned

The cloned project has its own gallery. Also sub gallery folders are cloned. If you have chosen to clone project files and snippets then the gallery will hold complete new instances of these resources. Else, the snippets and files are shared with the clone source.


 About HelpServer
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 About cloning
 Cloning folders and topics
 Cloning projects
 How shares and hyperlinks are treated in a clone
 Indicating candidate shares
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Including legacy content in real time
 Transferring objects between installations
 Customizing the look and feel
 User accounts
 Working with templates
 Working with metadata
 Workflow management
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript