Table of Contents
Advertisement
USING ROBOHELP HTML 10
Projects
5
Click Version Settings and then configure the following settings:
Require content approval for submitted items
Create a version each time you edit a file in this document library?
Note: The Create major versions option is also supported. In this case, files cannot be checked in as minor versions.
Keep the following number of major versions
Keep drafts for the following number of major versions
Who should see draft items in this document library?
Require documents to be checked out before they can be edited? (Force Checkout
Add a project to a SharePoint document library
1
Click Add to Version Control icon or select File > Version Control > Add to Version Control.
Select RoboHelp SharePoint Connector and click OK.
2
Specify the SharePoint site that contains the Document Library, and the username and password to log on to
3
SharePoint. Click OK to log on to SharePoint.
Note: You can use LDAP authentication if it is configured on the SharePoint server, by selecting the option Use
Windows Authentication.
When you connect to the SharePoint site, all the document libraries in that site are displayed.
Create a folder inside a document library or use an existing empty folder to upload the RoboHelp files and click OK.
4
RoboHelp adds the project files to SharePoint.
Note: You can add the project to any folder inside the document library. The folder must be empty. You cannot add
the project directly to a document library.
Merging Help projects
About merged Help projects
Using RoboHelp, you can create projects in an enterprise or distributed setup where different documentation projects
feed into a common project. You can achieve multi-authoring without using source-control software because multiple
writers can work on their individual projects and you merge them to create the common project. By using skins and
templates in the common project, you can achieve a unified appearance in the merged projects.
The merging takes place at run time, after the projects are generated. Before merging the projects, you simply place
references to other projects inside a master project (the master project does not actually contain the child projects).
You insert each reference in the master project's table of contents, placing it where you want the TOC of the child
project to appear. This step gives you control over where end users access the child project and gives the appearance
of a single, unified Help system. End users see a single online system complete with a table of contents, an index, full-
text search, a glossary (in WebHelp projects), and link controls.
Important: The child projects must not have content categories.
Merging multiple projects involves these steps:
• Create a master project with references to child projects in the TOC. See
Select No.
Select Create major and minor (draft) versions.
Deselect this option.
Deselect this option.
Users with read access.
Last updated 7/13/2012
Select Yes.
"Create a master
project" on page 99.
98
Advertisement
Table of Contents
