Standard Page and Content Page feature comparison

Standard Page basic components are not supported.

The combination of Component templates and Basic components required far more configuration to implement than the similar experience offered by Page Builder Core components for Content Pages.

Read the comparison page for more information: Basic components.

Component templates are used to apply pre-defined packages of code, HTML, and CSS to a Standard Page. This functionality is not supported on Content Pages. Instead, Page Builder offers Core components, a comprehensive list of commonly used components with styling instructions.

Read the comparison page for more information: Component templates.

With the introduction of personalization, this feature was excluded from Content Page assets due to potential conflicts between Content Page personalization and site-wide contexts.

The Personalization features offer better centralized control over personalization journeys for your website users.

Standard Pages offer page-level variations use evaluation rules an Personas to tailor content. Content in Page Builder is varied at the block level, instead, allowing for more precise control over what content presents.

Read the comparison page for more information: Page variations.

The goal of using Content Pages is to offer a simpler way of building rich content-based experiences using reusable components.

While keyword replacements offer a very powerful way to bring content in to pages, they can add unnecessary complexity to page builds and pose a steep learning curve to new content authors.

There are ways of including keyword-like behavior into Content Pages such as loading content from Standard Pages and rendering it using code. You build a reusable component that brings the content in programmatically instead of the keyword bringing in the content when the page renders.

Snippets, reusable pieces of content that can be added to Standard Pages using Keyword replacements, are not available in Page Builder. As a workaround, developers can create components with fixed HTML payloads and assign them to specific nodes, allowing content authors to select and apply the required snippet component to their pages.

Read the comparison page for more information: Snippets.

Nested content assets are not supported in Content Pages.

Nested content components are a feature of Standard Pages which allowed users to reference another system asset and have its content rendered in place on the frontend.

Although nested content components are not supported in Content Pages, it is possible to create components that can retrieve system asset info and render it on the frontend in much the same way. Read more about this approach in the Component Service documentation.

Basic audit information from an asset-level perspective is provided for the Content Page asset. Logging details about what content has changed in a component is passed to the DXP Logs service.

The asset version history is largely the same across Standard and Content Pages, with ony one major difference.

Read the comparison page for more information: Asset version history.

Workflow is supported for both asset types.

A/B testing is an exclusive feature only made possible through the architecture of the Page Builder service.