Initial Settings

When Paligo provides your organization with a Paligo instance, we recommend that you:

We do not enable consecutive branching and persistent image filenames by default as we need to ensure backwards compatibility with previous versions of Paligo.

We also recommend that you set up:

Note

You will need an admin user account to change the consecutive branching, persistent image filenames, and multi-factor login (2FA) settings.

By default, your Paligo instance is set to use English as the source language. This means that all topics and publications are marked up as English content. The source language is also used for various other parts of the content, such as labels that are auto-generated (for example for warnings, notes, etc).

If you write your content in another language, we can change the source language for you. Contact us at support@paligo.net .

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.

  1. Select Layout and edit the layout you are going to use for publishing.

  2. 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.

  3. 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 - the filename will be "layout-custom-style.css" every time you publish and this will not change.

  • Variable - Paligo generates a unique filename, so that the CSS filename changes each 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.

  1. Select Layout and edit the layout you are going to use for publishing.

  2. Select CSS, JS, logos and other assets.

    html5-layout-css-javascript.jpg
  3. Set Persistent Custom CSS Filename to Enabled.

    persistent-custom-css-filename.jpg
  4. Select Save.

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:

  1. Select Layout and edit the layout you are going to use for publishing.

  2. Enable the SEO-friendly output file names feature.

    Note

    The "reader-friendly" features require the SEO-friendly output file names feature to also be enabled.

  3. In the General section, enable or disable the Reader-friendly fragment identifiers (hash links) setting.

    hash-links.png

    Set to Enable to use text URLs.

    Set to Disable if you prefer to use the UUIDs for hashtag identifiers.

    Note

    Reader-friendly fragment identifiers is disabled by default, so that it does not affect any Paligo customers who want to continue using UUID in hash links.

  4. Select Save.

    Note

    If you have multiple topics or sections that become subtitles in the same publication with the exact same title, you would get duplicate hash fragment identifiers. If so, you can check the transformation log file (included in every output). Search for the phrase "Cannot generate reader-friendly hash link (fragment id)" to find them.

    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:outname attribute on the section element of each duplicate topic/section.

When you use the layout to publish your content, your chosen settings will be applied to the HTML output.

Branches are a way of creating different versions of your content. 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.

  1. Select your profile name in the upper right corner to display a menu, and then select Settings.

  2. Select the System Settings tab.

  3. Enable the Consecutive Branching feature.

    Consecutive branching feature shown with enable advanced branching turned on. This allows users to create a branch from another branch.

With persistent image filenames, Paligo uses a UUID (unique identifier) for each image. This means that images have an identifier that does not change, rather than a name that could change. As the UUID does not change, it is easier to manage updates as the names are always the same. and this is often better for managing updates.

We recommend that Persistent image filenames is enabled. If it is disabled, Paligo will generate random filenames for the images each time you publish.

  1. Select your profile name in the upper right corner to display a menu, and then select Settings.

  2. Select the System Settings tab.

  3. Enable the Persistent image filenames feature.

    Persistent image filenames setting with enable persistent filenames turned on. This means images use a static ID for the filename for HTML outputs.