Editor Settings
You'll find the Editor Settings inside the editor, in the toolbar:
![]() |
The Editor Settings dialog allows you to make the following settings:
Setting |
Description |
---|---|
Document validation |
Determines whether the document should be automatically validated, i.e make sure the underlying XML structure is correct, every time you save (recommended). |
Document check-in |
Determines whether the document will be automatically checked in when you close it (leave the editor). This is also recommended unless you specifically want to make sure no one can work on a set of documents for a certain period, in which case you can always disable it. |
Fix element structures |
When checked, if you have used element structures that may be problematic, they are automatically converted as soon as the document is saved. For example, lists, admonitions (notes, warnings, etc) or tables that have been nested in paragraphs are unwrapped. NoteThis setting is recommended for most users. While the nesting structures are formally valid in the DocBook schema, they are not recommended for a number of reasons, and this feature handles that. The only exception is if you have many such structures created previously, and have translated that content. If so, please check with support if this setting is right for you. |
Preview options |
This allows you to select which layout template to use for PDF, HTML, and HTML5 when you preview topics from within the editor. If you have a custom stylesheet or have created a custom layout of your own in the Layout Editor, you can select to always use that as your preview layout. |
Code editor |
In this setting you can choose the theme of your preference for the Code Editor, for example if you prefer a dark or light theme when viewing the source XML.f |
Editing |
In the Editing tab you can choose whether to use the Link tools for links and cross-references (recommended), and whether or not to have auto-save turned on in the editor. Autosave document is turned off by default, but is convenient if you do not always remember to save once in a while to avoid losing any work. If you do turn it on, auto-saving is done in the background without validation, so you won't be interrupted while you write content. So you should still save manually sometimes or just hit validate to make sure your content is valid. The Autoupdate title option means Paligo lets you automatically update the name of the topic object in the Content Manager. It will update when you change the title inside the topic. When enabled, the topic name (used for example in the content manager) is updated as soon as the document is saved. This option is set per author. CautionThis option is disabled by default, and you should only use it if you have no reason to keep the topic name and it's title separate. For instance, you may have several topics about the same subject matter, but for different products. In such cases you may want the same title but different topic names. If so, keep this option disabled. |
Global settings |
Set globally for all authors which elements should get an auto-generated id. Having these auto-generated is often useful as it for example makes it easier to link to internal elements. TipYou can also easily generate ids using the Element Structure Menu: ![]() NoteIf you change the default settings for which elements should get an auto-generated id, you should stick to only large block elements. It is not a good idea to set this for elements like |
Customizing the Editing Panel
By default, Paligo will highlight certain parts of the content to indicate the workflow status (released content will be green e.g), elements with comments (yellow), profiling/filtering ("funnel icon"), and which element has current focus (light blue).
You can customize this as you please, if you want a cleaner editing area without the status highlight for instance. Click to bring out the dropdown menu with the Editor Highlight Settings in the toolbar:
![]() |
Using the icon next to it, you can also choose to go into distraction free mode, if you want as much space as possible on the screen for your editor:
![]() |