About the Front Page document
The Front Page is the cover document of a publication in Pergamon. It’s generated through the Document Assembly workflow - Pergamon’s AI-assisted flow that builds a first draft from user inputs. Typical content includes the cover image, product name, model number, and required compliance elements.
Scope and layout requirement
Use the Front Page only with layouts of type Front. This guarantees correct processing and rendering in both Booklet and Leaflet publications. Assigning any other layout type can lead to formatting or pagination issues during PDF generation.
In practice, you only need to assemble and fine-tune a Front Page once. After you finish the first one, use it as a template: duplicate the document and reuse it across projects instead of rebuilding from scratch.
Anatomy of Front Page
The Front Page document is made of 6 content blocks, each with a specific purpose:
| Content block | Purpose | Description |
|---|---|---|
| 1 | Branding image | Upload the company or branding graphical image to this content block. Apply a different object style or use size adjustment to adapt the logo to the required size and position. |
| 2 | Product photo | Upload the product photo to this content block. The product image adjusts automatically based on the available space. The user does not need to manually resize it. |
| 3 | Compliance statement & symbols | Provide the compliance statement or upload compliance symbols to this content block, if it is mandatory for your product to appear on the front page. By default, this value is empty and you need to convert the content to Local to edit it. The content can be provided in one or multiple languages. |
| 4 | Product model number | Provide the product model number in this content block. |
| 5 | Product name | Provide the product name in this content block. Depending on the number of selected languages, the system will insert the required number of placeholders to be filled with the product name in each target language. |
| 6 | Document name and language ToC | Provide the document name in this content block. Depending on the number of selected languages, the system will insert the required number of placeholders to be filled with the document name in each target language. By default, Instruction Manual is used as the default document name. |
How to create a Front Page document
To create a Front Page document:
On the Home page, in Search, enter Front or Front Page.
In the results, locate Front Page, hover, and choose Create manual.
Answer the questions as prompted. After the document is assembled, click Confirm.
Enter a Document name and review the summary.
Choose Create to generate the document, then select Open Document to begin editing.
Edit Front Page document
Watch the video to see how to edit a Front Page document.
Prefer a new-tab view? Open the video.
Note: The video also covers Back Page editing. Once you’ve watched the Front Page portion, you can ignore the Back Page section if it’s not relevant right now.
Front page Document editing guidelines
-
Don’t add or delete content blocks. Although the Editor allows you to add or remove blocks, the Front Page layout is built on a fixed structure. Adding new blocks or deleting existing ones will break this structure and can cause layout-generation errors during PDF export.
- To ensure correct processing, edit only the text inside the existing content blocks. Keeping the original block structure intact prevents formatting issues and ensures the Front Page exports successfully.
- Front Page templates don’t consume tokens—if formatting breaks, you can reassemble the layout without extra cost.
- Keep the original block order. Don’t rearrange blocks to change the visual layout. If you need a different look, switch to a compatible Front Page layout instead.
- Don’t modify predefined script labels. Changing labels can cause PDF generation issues.
- No format-specific edits required. The same edited Front Page works for both Booklet and Leaflet publications.
Languages in Front Page Document
Language behavior on the Front Page
Multi-language mode (how it works)
The Front Page is always created in Multi-Language mode.
Because of this, it can’t be localized per language. If you need translations, paste them manually into the corresponding content blocks.
Language ToC content block
In multi-language assemblies, the system inserts language codes/markers to place the Front Page correctly in the publication.
Example (correctly configured for English-UK, German, French, Spanish, Polish):
Example snippet
EN Instruction Manual [|EN-GB|] DE Bedienungsanleitung [|DE|] FR Manuel d'instructions [|FR|] ES Manual de instrucciones [|ES|] PL Instrukcja obsługi [|PL|]
Formatting Language ToC block
Follow these rules to keep the language ToC working and paginated correctly:
Keep the special tab characters. Do not remove the Tab and Right-Indent Tab characters the system inserts in this block—they control the table-of-contents alignment.
Preserve the language-code syntax. Codes must remain inside square brackets with pipes, in the form
[|CODE|]or[|REGION-CODE|](e.g.,EN-GB). The system replaces this code with the final page number during export.Replace only the code placeholder. Swap the placeholder with the correct code from your supported language list; leave the surrounding brackets and pipes intact.
Example language ToC
EN Instruction Manual [|EN-GB|] DE Bedienungsanleitung [|DE|] FR Manuel d'instructions [|FR|] ES Manual de instrucciones [|ES|] PL Instrukcja obsługi [|PL|]
Keep the Tab and Right-Indent Tab characters
in this block; replace only the codes inside [|…|].
Common mistakes to avoid
Deleting the Tab / Right-Indent Tab characters (text will misalign and page numbers won’t render as expected).
Typing codes without brackets/pipes (e.g.,
EN-GBinstead of[|EN-GB|]).Renaming codes to non-supported values (use only valid language/locale codes).
List of supported language codes
Supported language codes
Use these codes inside the Language ToC block as [|CODE|] (for example,
[|EN-GB|]).
| Language | Code |
|---|---|
| Albanian |
SQ
|
| Bosnian |
BS
|
| Bulgarian |
BG
|
| Chinese (Mainland) |
ZH-CN
|
| Chinese (Traditional) |
ZH-CHT
|
| Croatian |
HR
|
| Czech |
CS
|
| Danish |
DA
|
| Dutch |
NL
|
| Dutch (Belgium) |
NL-BE
|
| English (UK) |
EN-GB
|
| English (US) |
EN-US
|
| Estonian |
ET
|
| Finnish |
FI
|
| French |
FR
|
| French (Belgium) |
FR-BE
|
| French (Canadian) |
FR-CA
|
| French (Switzerland) |
FR-CH
|
| German |
DE
|
| German (Austria) |
DE-AT
|
| German (Belgium) |
DE-BE
|
| German (Switzerland) |
DE-CH
|
| Greek |
EL
|
| Hungarian |
HU
|
| Icelandic |
IS
|
| Indonesian |
ID
|
| Language | Code |
|---|---|
| Italian |
IT
|
| Italian (Switzerland) |
IT-CH
|
| Japanese |
JA
|
| Kazakh |
KK
|
| Korean |
KO
|
| Latvian |
LV
|
| Lithuanian |
LT
|
| Macedonian |
MK
|
| Malay |
MS
|
| Norwegian |
NO
|
| Polish |
PL
|
| Portuguese |
PT
|
| Portuguese (Brazil) |
PT-BR
|
| Romanian |
RO
|
| Russian |
RU
|
| Serbian-Latin |
SR
|
| Slovak |
SK
|
| Slovenian |
SL
|
| Spanish |
ES
|
| Spanish (Guatemala) |
ES-GT
|
| Spanish (Mexico) |
ES-MX
|
| Spanish (Peru) |
ES-PE
|
| Swedish |
SV
|
| Thai |
TH
|
| Turkish |
TR
|
| Ukrainian |
UK
|
| Vietnamese |
VI
|
Comments
0 comments