A great place to post your ideas and vote on others so that you can let us know what is important to you.
Please take the time to register, and then share your detailed use case and how the proposed enhancements could provide value to your organisation.
We endeavour to provide an initial response to all ideas in a timely manner.
Our Experience Designers are always excited to talk to our customers about your experiences with the system. If you are keen to chat to them, you can easily book a short session with a member of the team right here.
Allow the user to clone an element to a saved library. User can then go to another page and clone the element to that page with all settings and content replicated.
|
What is the business process you are trying to achieve?
If I spend 20-30 minutes fine-tuning a block or row element (think: getting a video exacly right with backgrounds and paddings, or a "recent jobs" just the way I want it), add that to an "element library" so I can clone it to a completely different page with all settings intact. |
The ability to copy or clone an existing content row on a web page has been added to the system.
Details can be found on the Knowledge Portal in our release notes which are available here.
Content can now be copied to the same page, or to other pages within the site.
--
Steve Oxley
Product Manager
I wanted to provide a further update on this suggestion following some discussions with the engineering team.
Subject to technical feasibility once we start to look at building this out, we are planning to add capability for a user to be able to copy or clone a content row from a page in the CMS to either the same page, or another existing page.
We won't specifically create a library functionality as part of this enhancement, however, based on the planned capability, it would be possible for a user to create a non-linked page within the CMS which could effectively act as a library.
I will provide a further update once we commence work on this enhancement.
--
Steve Oxley
Product Manager
Thanks for providing this suggestion James.
I will discuss this item with our engineering team to assess the viability and potential complexity, and will revert back following that discussion.
--
Steve Oxley
Product Manager