Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Update Supported Data docs #251

Merged
merged 3 commits into from
Oct 18, 2024
Merged

Conversation

seangwright
Copy link
Member

Motivation

  • Update docs to match latest features/naming in Xperience by Kentico

Checklist

  • Code follows coding conventions held in this repo
  • Automated tests have been added
  • Tests are passing
  • Docs have been updated (if applicable)
  • Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test

If manual testing is required, what are the steps?

@Sapphirress
Copy link

Added to documentation backlog: DOC-2359

@peter-sipos peter-sipos self-requested a review September 27, 2024 11:50
Copy link

@peter-sipos peter-sipos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few details as per review comments that should be addressed.

@@ -23,11 +23,12 @@ Currently, the Kentico Migration Tool supports the following types of data:
- The migration includes the following versions of pages:
- _Published_
- _Latest draft version_ - for published pages, the version is migrated to the _Draft_ [workflow step](https://docs.kentico.com/x/JwKQC); for pages that do not have a published version, the version is migrated to the _Draft (initial)_ workflow step.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update "workflow step" to just "status" to make the terminology consistent with the update and with XbyK docs.

- Migration of Page Builder content is only available for Kentico Xperience 13.
- If you are migrating a Kentico 12 MVC application you can [upgrade it to Kentico Xperience 13 using the KIM](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/Usage-Guide.md#kentico-12-mvc) and then upgrade to Xperience by Kentico with Page Builder content.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is meant by "KIM" in the link text? Even in the link destination I haven't found the meaning. Preferably write the abbreviation out.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Kentico Installation Manager is known by the Kentico community as the KIM. I'll add the full name and the abbreviation in case anyone searches for KIM on this page.

- Each page gets assigned under its corresponding website channel.
- Linked pages are currently not supported in Xperience by Kentico. The migration creates standard page copies for any linked pages on the source instance.
- Page permissions (ACLs) are currently not supported in Xperience by Kentico and are not migrated.
- Page permissions (ACLs) are currently not supported by the Kentico Migration Tool and are not migrated. If you need page ACLs to be migrated, please [open an issue and request the feature](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/issues/new?assignees=&labels=&projects=&template=feature_request.md).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either go with "ACLs" or "page permissions" (preferably the latter), don't mix the two terms.

@seangwright seangwright merged commit bb7c100 into master Oct 18, 2024
@seangwright seangwright deleted the seangwright-patch-1 branch October 18, 2024 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants