---
title: Xperience essentials for solution architects
---

> 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).

This learning path is the starting point for designing an **Xperience by Kentico** solution. It covers how a project runs from first requirements to long-term maintenance, what the editors and marketers you design for actually do in the administration every day, and the first decisions you'll own: how content is modeled and where the solution runs.

These lessons are made for solution architects and technical leads joining their first Xperience project. You don't need to have built one before, and you won't write code here.

You'll learn how to:

- Run a project through its phases, from gathering requirements to maintaining what you built.
- Apply the practices Kentico solution architects use on real implementations.
- Recognize what editors do in the Content hub and what marketers do with campaigns and visitor data, so your design fits their work.
- Model content so it stays consistent and reusable as requirements grow.
- Find your way around the Kentico SaaS platform and Xperience Portal.

By the end of this path, you'll know how an Xperience project is shaped, who you're shaping it for, and where it runs – the grounding the deeper content modeling and upgrade paths build on.