Content governance considerations for commerce pages

When you configure your content item selectors, limit the allowed content types to only the content types that should be referenced. For your Product page, configure the Product selector to accept only Product content types (or specific product variants). This prevents editors from accidentally selecting the wrong content type.

For example, the following image shows that Kbank’s editors can select only product-specific content types, such as Loan, Account, Card, or Insurance, into the Product page thanks to the selector’s configuration.

Provide clear guidance for editors

Use descriptive field captions, like Select product, rather than just Product. Add helpful descriptions below the selector, such as Choose the reusable product this page will showcase. Include explanations about the content and its format to guide proper usage in all other fields.

The following image shows the product selector on the Kbank demo site. The page selector’s additional description tells editors to Select reusable Product item (Account, Loan, or Card) to display on your website., leaving little room for doubt.

Establish ownership and workflows before you start building content.

Decide who manages the reusable Product content items. Typically, this is a product team or merchandising team that owns the core product information, or data entry specialists who work closely with the product team. Decide who manages product wrapper pages. This is usually your marketing team or web content editors who control channel presentation and SEO.

The following image shows a product page approval workflow with three steps. Different stakeholders, such as content editors, product managers, and administrators, need to approve the page content before it’s published to the live site.

Plan your permissions and access structure

Use workspaces to organize content by team or business unit. For example, you can configure role permissions for each content type so the product team can edit Products but only view website pages, and the marketing team can edit wrapper pages but only view Products. To manage access to website pages, use the page level permissions.

As shown in the following image, editors on the Business Banking team can work only with content items that target their customer persona: B2B representatives. All products, product components, and articles filtered in the Content hub view fall under their business domain.

Understand publishing dependencies

When you publish a wrapper page that references an unpublished Product, you may need cascade publishing to publish all items together. When you update a reusable Product, remember that the changes will appear on every wrapper page that references it. Establish a notification process so teams know when shared content changes.

The following image shows a product page with all the unpublished content items this page references. Xperience cascade publishing allows publishing of all related content at once.

Multilingual considerations

When working with multilingual content, you need to decide what to translate and what to keep language-neutral. You can use AIRA translations to prepare content in different languages and then hand off different parts of the wrapper page to different editor teams via workflows.

One editor team might need to validate SEO metadata (title and description) for each language to ensure search results display correctly across markets. Social media managers might need to review translated Open Graph metadata to ensure social sharing displays properly in each language. Editors might need to customize the translation of language-specific CTAs and promotional text that appear only on that channel. Additionally, a product team might want to verify the translated product data in the Content hub.

Some content typically stays language-neutral. Core product data may or may not require translation depending on your markets and products. Product specifications often remain universal across languages. Product SKUs, prices, and technical specifications usually don’t need translation unless you have market-specific products.

Use Xperience’s language fallback feature appropriately. When a linked content item doesn’t have a translation in the target language, Xperience shows a yellow border warning in the editing interface. Decide whether to use the fallback language for untranslated linked items or require full translation before publishing in each language.