---
title: CI/CD
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

**Continuous Integration** and **Continuous Deployment** (CI/CD) enable Xperience projects to work in an automated software development and deployment flow.

Both features serialize the data of objects from the database into XML files within a **repository** on the file system. These repositories can then be restored into an Xperience database in a desired environment.

### [Continuous Integration](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-integration.md)

With Continuous Integration enabled, the system tracks local changes made to database objects, and automatically transfers them to the developer's repository. Developers track the CI repository in a [source control system](https://en.wikipedia.org/wiki/Revision_control) (for example, [Git](https://git-scm.com/) or [Subversion](https://subversion.apache.org/)) together with other code and project files. The repository is then used to synchronize database data between team members.

### [Continuous Deployment](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-deployment.md)

Developers prepare new projects or updates for existing ones within a dedicated development environment. Once the project is ready to be published, data from the development database is stored into a CD repository, which is then deployed to another Xperience instance in a staging, UAT or production environment.