Document360 Import Specifics
During the Document360 zipped project import, common elements like paragraphs of text, images, and links are imported as they are. However, the import of Documen360-specific entities has its specifics and limitations. This topic describes these specifics in detail.
Document360 Import Limitations
Below is a list of the import process's limitations and how ClickHelp handles these cases.
|
Document360 entity
|
Processing by ClickHelp
|
|
|---|---|---|
|
LaTeX equations
|
Imported as text.
|
|
|
Private Notes
|
Not imported.
|
|
|
Variables
|
Since variables' values are not included in the Document360 export archive, ClickHelp creates the corresponding project-level Variables, using their titles as their values. Correct the values manually if needed. |
|
|
Snippets
|
Since snippets' content is not included in the Document360 export archive, ClickHelp creates the corresponding Snippets without any content. Add the content manually if needed. |
|
|
Glossary terms
|
Imported as text.
|
|
|
The Index category type
|
Imported as folders. Since folders don't have their own URLs in ClickHelp, all the corresponding links to the Index category type will lead to the 404 page after the import. |
| Tags are not included in the Document360 export archive. If you want to have the same functionality in ClickHelp, you will need to set up Index Keywords manually. |
Workspaces Import Specifics
The Document360 workspaces concept is different from our approach to working with projects. However, the closest entity to the workspace in ClickHelp is the project, so each workspace is imported as a separate project in ClickHelp with its own set of variables and snippets. If the archive you are importing contains multiple workspaces, the system will prompt you to select the single specific workspace you want to import now.
If necessary, other workspaces can be imported as individual projects by repeating the import process for each workspace.