The content slug is part of a content element. The slug describes a part of the url, that is used to address this content element.

For example, a content might have the following url: http://company.indoc.pro/project/latest/document/content-level1/content-level2 In this case, content-level1 and content-level2 is the slug of each of the content pages.

It can be used for the following use cases.

Content Slug for language specific urls

If the portal should contain language specific urls (e.g. for seo reasons, to make it more user friendly), the content slug should be left empty. Then indoc automatically generates the content slug based on the language specific, translated title of the content page.

Content Slug for language independent urls

If the portal should contain the same urls for all content pages (e.g. for better linking from external systems), the content slug should be set. Then indoc uses this content slug for all languages.

Example

Content page title is "My content" in English, and "Mein Inhalt" in German. The content is used in the project "my-project" and document "introduction".

If the language independent content slug is not set, the content will be available at the url-slug "my-content" in English, and "mein-inhalt" in German. The public url will be:

If the language independent content slug is set to e.g. "my-content", the content will be available at the url slug "my-content" in English and in German.

The public url will be:

Suggestion

If you want to reference specific content pages from external systems, set the content slug for each page manually. This content page uses a language-independent slug "content-slug", so it can be referenced from the (external) application's edit form. If you do not want to reference or link the content pages from external systems, than it can be kept empty and the language-specific slug will be used. This can be useful for documents that have a lot of (unstructured) content pages, as e.g. user manual or operating manual.


Download as PDF