Content Sync for outside of pages/reusable

Hi,

We're migrating our website from v13 to Xperience. We're currently working on setting up the sync between our environments. And... I see a lot of things missing.

  • We don't have a list of changed things anymore. In v13, you were able to know what had changed and to trigger the sync. I don't see this functionnality anymore as the only place to sync is now from listings (pages or reusable contents)
  • How to sync modules ? Do we have to implement a custom action on the interface to allow that ? Is it even possible ?
  • Settings ?

I feel the "staging" feature has been dropped and replaces with a "content sync" one but it leaves a lot of gaps to be able to work correctly.

What's your vision about getting a new module to production ?

Environment

  • Xperience by Kentico version: [31.2.0]

  • .NET version: [10]

  • Execution environment: [Private cloud (Azure)]

Tags:
Content management Content sync v31.2.0 Deployments
0

Answers

Hi @CDumange,

From our hands-on migration from Kentico 13 to Xperience by Kentico, we've discovered a game-changing shift in how to move changes between environments! The old "stage everything" model is now brilliantly split into two powerful paths: content sync for editor content and CI/CD for system/schema changes.

Observations

In Kentico 13, staging could sync many object-level changes like page type definitions, custom tables, and forms. In Xperience by Kentico, content sync is mainly for actual content such as website pages, content items, and reusable content, while core object definitions and system/configuration items should be handled through CI/CD or Continuous Deployment depending on the object type. So the model is now more split: content goes through content sync, and platform/code/schema changes go through deployment pipelines.

Objects that belong to Content sync

These are the items Xperience by Kentico treats as content, not platform configuration or outside objects:

  • Website pages.

  • Content hub content items.

  • Reusable content items.

  • Reusable field schema

  • Forms when you synchronize them as content.

  • Linked pages/items, assets, taxonomy tags, and related content that are part of the synchronized content.

Objects that belong to CI/CD or deployment

These are the items that should be moved through Continuous Integration / Continuous Deployment or SaaS deployment, not content sync

  • Content types and reusable field schema type definitions.

  • Form definitions and form builder components.

  • Channel definitions and channel settings.

  • Workspaces.

  • Languages.

  • Member roles.

  • Object type definitions and other system object metadata.

  • Custom modules or custom integrations

  • Code components such as page views, controllers, view component's, custom page builder components, custom form builder components, and sections.

    Thanks

    Nikhila

0

That's a beautiful answer (even if it smells IA very strongly).

CI and Staging were already existing in v13 so it's nothing new. My problem is that the "staging" feature has been demoted to a "content sync" and that it does not fill the same niche.

Here are a few cases that are absolutely not answered:

  • You add a new image/page/xxx to qa. How do you know (as webmaster/admin/whatever) that ? How do you retrieve content that has not been synched ? Do we have to keep a list and do it by hand ? Guess ? Sync whole folders just to be sure (when it's not recommended in the doc)
  • As of my test, modules values are not included in the CI in Xperience (they were in v13). Am I suppose to fill them by hands ? I have modules with hundred of values...
0

These aren’t edge cases, they represent real, day-to-day workflow gaps that can affect teams migrating from v13. I’d strongly encourage raising them on the Xperience by Kentico - Roadmap board with clear, concrete examples to help increase visibility and drive prioritization.

0

To response this discussion, you have to login first.