Enable Cloning of Individual Components in Component Service
planned
Garrett Levy
There should be a native way to clone individual components on Content Page page types, similar to the cloning functionality that existed for CCT components on Standard Pages.
I understand that components on Content Pages do not have their own standalone asset IDs. However, if this could be implemented through the use of shadow child assets, it would help restore a workflow that previously provided significant efficiency gains. Ideally, these shadow child assets would be visible and selectable within the asset tree, allowing users to right-click and clone or move components to another page or duplicate them on the same page.
This would effectively replicate the component reuse capabilities available on Standard Pages and would greatly improve content authoring efficiency.
Today, if I want to create five variations of the same component on a Content Page, I must manually create each component and repopulate all fields from scratch. On a Standard Page, I could create the component once, clone it four times, and then make only the incremental changes required for each variation. The current workflow introduces significant repetitive effort and makes experimentation, content testing, and reuse much less efficient.
Cam Ross
updated the status to
planned
Cam Ross
Hi Garrett,
Great news! Your request aligns directly with our upcoming product vision. It is currently planned on our roadmap for release around the 2nd quarter of 2027.
Thank you for helping us make our platform better!
Best regards,
Cam, Product Lead
M
Manjeet
Yes, this is on our wishlist too. It would be great to have this functiionaliuy in Component Service.
R
Rebecca Larson
This is really big on our wish list, too!