---
title: Commerce presentation components wrap-up
---

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

## Summary

> **Key:** **Key takeaways**
>
> - Presentation components in XbyK follow a hierarchy: _Page Template → Section → Widget → Content Item_.
> - Classify widgets into three patterns based on how they source content: **Mixed content** (_Content hub_ reference + overrides), **Referenced content** (_Content hub_ reference only), and **Stored content** (page-specific).
> - _Mixed content_ widgets are the recommended default for commerce scenarios - they let editors run campaigns and optimization tests without altering canonical content.
> - Keep widget properties under 15 per widget, group them logically, and use conditional visibility to manage complexity.
> - Establish governance rules for templates, sections, and widgets to balance editorial flexibility with brand consistency.

With your presentation components designed, you have the building blocks editors need to create commerce pages. Pair this with your [commerce content types](https://docs.kentico.com/modules/commerce-content-modeling/model-commerce-pages-intro.md) to complete the content model.