---
title: Establish content governance for commerce presentation components
---

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

## Establish content governance for presentation components

Presentation components need governance rules that define who can create, modify, and use them. For some of the following situations, Xperience doesn't provide built-in restrictions that automatically ensure consistency, so you need to establish the governance guidelines outside of Xperience, for example, within the editor team's documentation.

**Template governance:**

- Define which roles can decide which templates are available for each website channel.
- Establish an approval process for new template requests.
- Document the purpose and intended use of each template.

**Section governance:**

- Decide whether all sections should be available in all templates, or restrict specific sections to specific templates for brand consistency.
- Require designer approval for custom section requests that go beyond the predefined set.

**Widget governance:**

- Control widget availability per template - campaign templates may offer all widgets, while product detail templates offer a curated set.
- Define override permissions: who can override referenced content with promotional messaging?
- Establish ownership for optimization and approval workflows - not every editor should be able to launch a promotional override without review.
- Create a review process for promotional badges and campaign-specific messaging.

**Best practices for governance:**

- Document the purpose of each component so that new team members understand the design decisions.
- Create component usage guidelines for editors with examples of when to use each widget pattern.
- Define clear rules for when to use Mixed content, Referenced content, and Stored content patterns.
- Balance flexibility with consistency - too restrictive prevents editors from responding to marketing opportunities, too permissive creates brand inconsistency.