Before you start authoring, we recommend that you set up your Paligo instance. There are various settings that we recommend that you put in place. We categorize these settings as:
-
Recommended System Settings - System settings that affect the entire instance. Typically an administrator-level user applies these when they first set up a Paligo instance.
-
Recommended Layout Settings - Layout settings apply whenever you publish using a particular layout. Many layout settings are optional and you can alter them to suit your own requirements. But a small number of them are recommended as best practice, so putting them in place is a good idea.
-
Preferences for Individual Users - Settings that only affect your particular user account, such as your Editor settings. Typically, each user sets these preferences when they first start using Paligo.
Note
We do not apply these settings by default as we need to ensure backward compatibility with previous versions of Paligo.
You will need an admin user account to change the consecutive branching, persistent image filenames and multi-factor login (2FA) settings.
Paligo has some system-wide settings that affect your entire instance. For these, we recommend that you:
-
Control the Image Filenames in the system settings.
-
Choose your preferred deletion strategy, see Allow Users to Delete or Force them to Send to Trash.
When you have applied the recommended system settings, move on to setting the Recommended Layout Settings and Preferences for Individual Users.
Note
If you are on the Paligo Enterprise plan, we recommend setting up Two-Factor Authentication (2FA).
Paligo uses layouts to store all of your preferences for publishing. There are built-in layouts for the various different types of Paligo output, including PDF, HTML, and HTML5. You can also create your own custom layouts for the different output types. To learn more, see Layouts. For each layout that you intend to use for publishing, we recommend that you:
-
Choose your Filtering Strategy. This determines whether you can use Scoped Filtering. You enable or disable it in the layout settings.
-
Control the Custom CSS Filename in the layout settings.
-
Set Up SEO-Friendly and Reader-Friendly URLs in the layout settings. This only applies to HTML-based layouts.
Layouts have many other settings that you can use to customize your outputs to suit your requirements.
Tip
To enable the usage of more than 9 subsections in a topic, the checkbox Save can be cleared under Paligo Recommended Rules in the Editor Settings. However, the best way is to Use Components to Create Subsections.
We recommend that each user sets their own time zone and also chooses their own preferences for the Paligo editor. To make your choices, see:
Paligo has two different filtering strategies for controlling whether content is included or excluded when you publish. The strategies are known as "normal" filtering and "scoped filtering" and you need to choose which strategy to use before you publish.
To choose the strategy for a publication, use the layout editor.
-
Disable Use Algolia Search.
-
Locate the Enable scoped profiling/filtering option.
For PDF layouts, you can find the setting in General > Filtering and taxonomies.
For HMTL layouts, it is in the Classes and Attributes settings.
-
Choose the strategy that will be used when you publish.
-
Set Enabled scoped profiling/filtering to No to use normal filtering.
-
Set Enabled scoped profiling/filtering to Yes to use scoped filtering.
-
Important
We recommend that you set Enabled scoped profiling to No unless you have a specific requirement for scoped filtering. Scoped filtering is designed for when you reuse filtered content in the same publication, but want different values to apply. To find out more, see Scoped Filtering
You can upload your own CSS file to an HTML layout to customize the styles that are used in your HTML output. The filename for the CSS can be:
-
Persistent
With the Persistent custom CSS filename feature enabled, Paligo will set the CSS filename to "layout-custom-style.css". This is fixed and will be used every time you publish.
-
Variable
With the Persistent custom CSS filename feature disabled, Paligo will use a different, unique name for the CSS every time you publish.
We recommend that you enable persistent CSS filenames, unless you have a specific need for a different CSS filename each time you publish.
If you are publishing to HTML, you will need to use one or more HTML layouts. The layouts have default settings in place that are designed to provide a good starting point.
By default, the HTML layouts have the "SEO-friendly URLs" and "Reader-friendly URLs" features disabled, as this is needed for long-term Paligo customers. But on new Paligo instances, it is better to have these settings enabled.
To set up SEO-friendly and reader-friendly URLs:
-
Disable Use Algolia Search.
-
Enable the SEO-friendly output file names feature.
-
In the General section, enable or disable the Reader-friendly fragment identifiers (hash links) setting.
Set to Enable to use text URLs.
Set to Disable if you prefer to use the UUIDs for hashtag identifiers.
-
Check the box Use gateway to enable IP Allowlisting. Optional
Note
If you have a publication that contains multiple topics or sections with the same title, you would get duplicate hash fragment identifiers.
If you have such duplicates, Paligo will add a suffix to differentiate them. The suffix is generated from the id of the second topic/section. But you can avoid using suffixes by manually providing a reader-friendly fragment identifier. To do this, use the
xinfo:outnameattribute on thesectionelement of each duplicate topic/section.
When you use the layout to publish your content, your chosen settings will be applied to the HTML output.
Paligo has a branching feature that is designed for creating and managing different versions of your content. You can find out about how it works in Branching.
Depending on how you want to use branching, you can set Paligo to:
-
Only allow a branch to be made from an unbranched publication or topic. With this approach, you cannot make a branch of another branch.
-
Allow branches to be made from other branches.
For example, you could create a branch of version 1.0 of a publication to create a version 2.0. When you enable the consecutive branching feature, it means you can create a new branch from an existing branch.
To enable or disable consecutive branching:
With persistent image filenames, Paligo uses a UUID (universally unique identifier) as the filename for each image. This UUID will always remain the same, so even if the name of the image would change in Paligo, the filenames in the outputs would always stay consistent.
We recommend that you enable the Persistent image filenames feature. If you disable it, Paligo will generate random filenames for the images each time you publish.
Paligo can automatically log out inactive users. This can be important for complying with security policies and reducing the risk of unauthorized users gaining access to Paligo and your content.
Paligo has a Source Language Translation Import feature that, in most cases, should be disabled. It is designed for use in unusual scenarios where multiple languages are used for authoring.
To check that it is disabled (or to enable it, if you have been advised to by Paligo customer support):
Paligo has two deletion strategies and you can choose which one you want to use.
-
Users can delete content directly from the Documents section of the Content Manager.
This content is immediately deleted from the database. It can be restored from the Activity Feed if needed.
-
Users do not have access to the delete option in the Documents section. They can only move content to the trash. Once the content is in the trash, they can either restore it or they can delete it. You may prefer this two-step process as it can be quicker and easier to restore from the trash rather than finding the deletions in the Activity Feed.
To choose the deletion strategy for your Paligo instance:
-
Select your profile name in the upper right corner to display a menu, and then select Settings.
-
Select the System Settings tab.
-
Use the Enable deleting content option to choose your deletion strategy.
-
Enable the option to allow users to use the Delete option directly from the Documents section of the Content Manager
-
Disable the option to deny access to the Delete option in the Documents section. Users can only send the content to the trash (but they can delete it from there, if needed).
-
Administrators can create a template to define the structure of filenames. Paligo will use the template by default when it generates filenames for the PDF and ZIP files it publishes.
Note
When users publish content in Paligo, they can use publish document dialog to set a different filename structure. If they do this, Paligo will use the publishing settings instead of the default system settings. To find out more, see General Publishing Process.
To define the default filename structure:
-
Select the avatar in the top-right corner.
-
Select Settings from the menu.
-
Select the System settings tab.
-
Use the Output filename template setting to control the filename of the output. Default is:
ID-Title-Format.You can set it to include various values:
-
ID - The ID of the document.
-
Title - The title of the publication or topic that you are publishing.
-
Format - The name of the output format, for example, PDF or HTML5.
-
Edit date - The date that the publication or topic was last edited.
-
Branch label - The text from the branch label for the publication or topic. This only applies if your content has been branched and it has a branch label. For details, see Add or Edit Branch Labels.
-
Unique value - A random string of characters, generated by Paligo, that is added to the filename to make it unique. This can stop the file from being overwritten by later publishes of the same document.
-
-
Select Save template.
The next time a user starts the publishing process, Paligo will use this template as the default for naming the output files. If a user enters different filename syntax in the publishing settings, Paligo will use those instead.
Comments
0 comments
Article is closed for comments.