Imported pages
Recognize the pages that come from a product's repository, understand why they aren't edited in Elion ITSM and review the report of each import.
On this page
Some spaces aren't written in Elion ITSM: their content comes from a product's documentation, which lives in files inside its repository. Every time that documentation changes, it's imported into the space. That way the documentation has a single source and there are never two different versions of the same text.
How to recognize an imported page
When you open an imported page you'll see, above the content, the message Imported from followed by the path of the source file. The message says the page is edited in the product repository and is read-only in Elion ITSM.
On an imported page:
the Edit, Subpage, Move, Archive and Delete buttons don't appear;
if you try to open its editor, you'll see that the page is imported from its source file and is read-only here;
you can read it, see its History, use Copy link and leave Comments if you can edit in the space. Mark resolved doesn't appear on these pages.
Why isn't it edited here? If someone fixed the page in Elion ITSM, the next import would bring back the repository text and the change would be lost. To fix an imported page, let the team that maintains the product documentation know. A comment on the page is a good way to leave the notice.
What each import does
Each file in the repository matches one page, and it's always recognized by its path. In each import:
a new file creates a page and publishes it;
a file that changed creates a new version of its page and publishes it, with the note Imported in the history;
an unchanged file doesn't touch its page;
a deleted file archives its page, it doesn't delete it. If the file comes back, the page comes back with the same number.
If a file is marked as a draft in the repository, its page stays as a draft instead of being published.
Everything is recorded in each page's history, like any other publication (see History and versions).
See the import report
Before you start
You need Manage in Knowledge (Administrator role).
Steps
Go into the space.
Press Imports. Imports of and the space name opens.
Review the list. Each import shows:
the date and how long ago it was done;
the source: Terminal, Uploaded zip or GitHub Action;
the repository version that was imported, if it was given;
the summary, for example "3 created · 1 updated · 12 unchanged". It also reports the archived ones. If there were no pages, it says No pages.
If the import had warnings, press warnings (with its number) to see them. Each one shows the file and what happened.
Press Close to leave.
If the space has never received an import, you'll see This space has no imports yet.
What the warnings mean
Warnings don't stop the import: they flag something worth fixing in the product repository. The most common are:
a text element the knowledge base doesn't support, which was skipped;
a missing image or a broken link;
a file that was ignored because it's not a page or an image, or because it's too large.
Review the report after each big change to the documentation. Fixing the warnings in the repository leaves the pages complete in the next import.