Reading time: 6 min read
Sitecore XM Cloud New Release for Content Editing in Page Builder
Explore the new XM Cloud editing interfaces that let authors modify content not visible on the page, including supported field types.
Page and Data Source Content Editing Improvements
Sitecore has introduced an exciting new feature that enhances the authoring experience in XM Cloud: the ability to edit page and data source content fields directly within the Page Builder. This is a big step toward adopting Page Builder, making it easier for authors to modify written content while maintaining full visibility of the page presentation.
Previously, authors could only modify simple fields rendered on the page and Rendering Parameters in the right pane, allowing them to adjust settings related to a component’s presentation but not its actual content. Full control over most of field types is now available.
New Page Builder Features
With this release, you can now:
- Edit content fields associated with the page, including metadata, in the Page Content pane.
- View and modify content fields while previewing the page presentation.
- Expand the content view to a full-screen mode that persists across pages.
- Edit data source item fields included in components by selecting the component and using the Content tab in the right-hand panel.
- Have all content edits automatically saved and instantly reflected in the page’s presentation.
- Use Undo and Redo options as long as you remain on the edited page.
XM Cloud Page Builder with Page content in the left and Data Source content in the right pane.
Positive Takeaways
- Modern and intuitive interface for all the supported types.
- Workflow works, automatically creating a new Draft version for Page and Data Source items.
- Auto Saving, likewise in-page edit, also available in the new interfaces.
- Publishing and workflow approvals can all be done in the interface without leaving Page Builder.
- It does respect Item Level Security not allowing authors to change content with no Write permissions.
Areas for Improvement
The issues appointed below are true at the time of publishing of this article. Some issues will definitely be fixed over time.
- It does not respect Field Security, allowing authors to change the value even with no Field Write permissions.
- It works and enforces item level security by showing an error message, however, disabling the controls would be a better user experience.
- Interface shows Field Name instead of Title.
- You cannot sort the sections in the interface, it is not alphabetical either.
- There should be available a way for developers to hide fields from the new interfaces in Page Builder.
- The Help’s Short Description in a field could be present as a tooltip.
Field Type Support
Below, you will find a table listing all the supported fields in the new interfaces for page and data source content edit, along with their corresponding replacements (when available) for any fields that are not supported. Additionally, you will find a script that can help you identify any unsupported fields in your current setup.
Simple Types
| Type Name | Supported in Page Builder | Alternative Replacement | Interface |
|---|---|---|---|
| Single-Line Text | Yes | - | Single Line Text |
| Date | Yes | - | Date Picker |
| DateTime | Yes | - | Date and Time Picker |
| Checkbox | Yes | - | Checkbox |
| File | Yes | - | Custom Dialog |
| Image | Yes | - | Custom Dialog |
| Integer | Yes | - | Single Line Text |
| Multi-Line Text | Yes | - | Multi Line Text |
| Number | Yes | - | Single Line Text |
| Password | No | Not available | - |
| Rich Text | Yes | - | Rich Text Editor |
List Types
| Type Name | Supported in Page Builder | Alternative Replacement | Interface |
|---|---|---|---|
| Checklist | Yes | - | Checkbox List |
| Droplist | Yes | - | Dropdown |
| Grouped Droplist | No | Droplist* | - |
| Grouped Droplink | No | Droplink* | - |
| Lookup Name Lookup Value List | No | Not available | - |
| Multilist | Yes | - | Checkbox List |
| Multilist with Search | No | - | - |
| Name Lookup Value List | No | - | - |
| RedirectMap | No | - | - |
| Treelist | Yes | - | Tags Multi List |
| TreelistEx | No | Treelist | - |
| Taglist | Yes | - | Tags Multi List |
| TagTreelist | No | Taglist* | - |
| Multiroot Treelist | Yes | - | Tags Multi List |
Link Types
| Type Name | Supported in Page Builder | Alternative Replacement | Interface |
|---|---|---|---|
| Droplink | Yes | - | Dropdown |
| Droptree | No | Droplink or Treelist* | - |
| General Link | Yes | - | Custom Link Interface |
| General Link with Search | No | General Link* | - |
*The Alternative Replacements does not fully substitute the original type, but it makes it possible on Page Builder.
# Identify unsupported fields in Page Builder's "Page content" interface
# Replace the Path
$items = Get-ChildItem -Path "master:/sitecore/templates/Foundation" -Recurse
$typeMappings = @{
"Single-Line Text" = "Supported"
"Date" = "Supported"
"Datetime" = "Supported"
"Checkbox" = "Supported"
"File" = "Supported"
"Image" = "Supported"
"Integer" = "Supported"
"Multi-Line Text" = "Supported"
"Number" = "Supported"
"Rich Text" = "Supported"
"Checklist" = "Supported"
"Droplist" = "Supported"
"Multilist" = "Supported"
"Treelist" = "Supported"
"Taglist" = "Supported"
"Droplink" = "Supported"
"General Link" = "Supported"
"Multiroot Treelist" = "Supported"
"Password" = "Not Supported"
"Grouped Droplist" = "Not Supported - Consider using Droplist Instead"
"Grouped Droplink" = "Not Supported - Consider using Droplink Instead"
"Lookup Name Lookup Value List" = "Not Supported"
"Multilist with Search" = "Not Supported"
"Name Lookup Value List" = "Not Supported"
"RedirectMap" = "Not Supported"
"TreelistEx" = "Not Supported - Consider using Treelist Instead"
"TagTreelist" = "Not Supported - Consider using Taglist Instead"
"Droptree" = "Not Supported - Consider using Droplink or Treelist Instead"
"General Link with Search" = "Not Supported - Consider using General Link Instead"
}
foreach ($item in $items) {
if ($item -ne $null -AND $item.TemplateName -eq "Template field") {
$type = $item["Type"]
if ($typeMappings.ContainsKey($type)) {
$supportStatus = $typeMappings[$type]
} else {
$supportStatus = "Not Supported"
}
if ($supportStatus -ne "Supported") {
Write-Host $item.ID " => Type: $type - $supportStatus"
}
}
}
Final Thoughts on the New Page Editing Experience
This new interface is a big step for Page Builder. It significantly enhances the content editing experience with highly anticipated features. The supported list of fields is comprehensive and covers a large range of requirements. There are still some important gaps, however, which will need attention for a better and customized user experience.