Content is created and managed inside Kentico Xperience
If content is managed this way, the developers must prepare the data structures and storage before content can be entered. If the project is already live, we recommend using a staging environment for content creation rather than directly editing in the production environment.
Content is created and managed outside of Kentico Xperience
This content is typically used for items like a product catalog and is either synchronized to Kentico using custom-built scheduled tasks, e.g., using Hangfire or Quartz.NET, or pulled directly from the external system at runtime (e.g., web services, SDKs, etc.).
Content migrated to Kentico
A partner was migrating to a client's web site from an existing CMS. Since the CMS had most of the content stored in a structured fashion, they decided to import the content using the Kentico API.
As they completed the data structures for each type of content, they created a simple one-time import tool to map the content from the old CMS to the Xperience data structures.