A Topic is a preconfigured container that holds multiple content units. Each Topic is a reusable collection of content that has been pre-styled with the correct headers, body text, lists, warnings, tables, or other formatting.
When you add a Topic, Pergamon inserts its content into new content blocks according to the Topic’s predefined structure. This provides a complete, styled block sequence that helps maintain consistency and reduces the need to manually create or format content.
Before you begin
-
You have access to the document.
If you are not the author, request access permissions from the author.
If you see the document is locked for editing, contact the author to release the lock.
Open an existing document in the Editor.
Make sure single-session editing mode is enabled.
Add content from Topic
-
Select the content block where you want to insert the Topic.
The location you select determines how the Topic will be placed within your document structure.
In the Editor, click Add a Topic in the right-side toolbar.
(Optional) Use the Category dropdown or Search field to find the Topic you need.
Click the + icon next to the Topic to insert it.
(Optional) Select Place at document start to insert the Topic at the beginning of the document.
When you add a Topic, Pergamon inserts a set of preconfigured content as new content blocks in your document. These blocks are inserted as Global content, which preserves their original structure and styling. Global content includes:
Grey background
A chain/link icon
Type: Global in the Content Attributes panel
A Source field that displays the Topic ID used
(for example: “Manually added global content from topic IT01582”)
How Pergamon selects Topic content based on language
Topics often contain multiple content units, and each unit may exist in different languages. When you add a Topic, Pergamon inserts only the content units that match your document’s language.
How it works:
Pergamon checks the document language (for example, PL).
It evaluates each content unit inside the Topic.
- Units that include a language that is the same as in the document language are inserted.
Units without a matching language are skipped.
If none of the content units match, the Topic cannot be added and the error appears.
Example
Scenario 1: Document language PL
Topic has 3 content units, but only IC00002 has PL
→ IC00002 is inserted
Scenario 2: Document language PL
None of the items have a PL version
→ Error appears
How Topic placement works
The structure of your document is organized in parent (Header) blocks and nested child blocks. When you add a Topic, Pergamon inserts it based on the block you selected in Step 1.
If you select a parent Header block (H1)
If the Topic begins with non-header content (Body, List, Warning, etc.):
→ All Topic content is inserted as child blocks under the selected H1.If the Topic begins with another H1 parent header:
→ A new H1 block is inserted below the selected H1, not nested inside it.
If you select a sub-parent block (H2–H5)
All Topic content is inserted as child blocks under that selected header, following the hierarchical structure.
Edit a Topic
Editing a Topic involves editing the content added as part of the Topic. A content or units of content part of the Topic are added as Global content blocks and cannot be edited until unlocked.
Convert Global content to Local
To unlock and edit a content block:
macOS: Shift + Command (⌘) + L
Windows: Shift + Ctrl + L
After conversion:
The block background turns white.
The chain icon disappears.
The block becomes local and fully editable.
Troubleshooting
Issue
Topic has no content in the document’s language
Cause
The Topic does not contain any content that match the current document language. Because none of the content units support this language, Pergamon cannot insert the Topic.
Resolution
Contact your designated Knowledge Engineering team in your organization.
Comments
2 comments
Please blur the client’s name in the Step 4 image as well, for consistency. Thanks.
Hi @celline, thanks for your feedback. That's a good catch. Client's name is now masked in all screenshots. Community engagement from Pergamon users on help articles are highly appreciated and valued.