Standard page and content page feature comparison
While the content page asset offers an evolving editing experience, there might be situations where the existing standard page asset is a better choice for some content challenges.
This feature comparison between standard page and content page asset types aims to help guide you toward the right asset solution to choose when designing your website pages.
|
The term legacy in this reference table refers to existing features found in the Content Management service. It does not imply that features are planned to be deprecated. |
| Feature | Standard | Content | Clarifications |
|---|---|---|---|
Legacy content components |
Yes |
No |
Standard page content components are not supported. Page Builder Core components provide a modern replacement. |
Legacy contexts |
Yes |
No |
This is a legacy Content Management Service feature. |
Legacy variations |
Yes |
No |
Page Builder offers a different approach to content variations in the Content Management Service. |
Modern variations |
No |
Yes |
Page Builder uses modern variations for the following features:
|
Keywords |
Yes |
No |
While keywords are powerful, they add complexity to page builds that do not serve the goals of a modern page-building experience. To iterate on the role keyword replacements offer in a modern page-building experience, you could consider the component model as solving one common goal of keywords, being a way to load content from standard pages and render it using code. You can build this using a custom component deployed through the Component Service. |
Audit logs |
Yes |
No |
Basic audit information from an asset-level perspective is provided for the content page asset. Logging details about what text has changed in a component block is unavailable. This level of detail is highly desirable and is on the roadmap. |
Asset version history |
Yes |
No |
There is no asset version history capability for content pages. Therefore, the Version History menu option in content page assets is unavailable. |
Workflow |
Yes |
No |
Workflow is a legacy Content Management asset feature and, therefore, is incompatible with the modern page builder architecture. |
A/B Testing |
No |
Yes |
A/B testing is an exclusive feature only made possible through the architecture of the Page Builder service. |