In our daily work we are facing a challenge when it comes to maintaince of email templates build from fragments. We are using different pre-defined templates that is built from fragments. And the fragments again contains just dummy images and lorum ipsum texts. The users changes the content in the fragments when they create there Journeys with there emails. The issue we are facing is when a content designer wants to change the template that is in use in an running Journey – there will be a problem. The content designer could have ordered a total new template, with a new look that he wants to use (a new framwork) or simply just want to change to another existing template (could be seasonal variations in the design). When you use the “change design” feature in the email, and changes to another template – you use all your created content in that email you are changing design too. It should have been possible to keep your content when you change the underlaying template.
Maybe it could be solved buy having a export content feature, that takes all HTML code from the “Drag and Drop” container, and make this possible to import into the new template you have selected. The code is there, it is just to move it into the new selected template -and store it. That could have been an option when changing the design – move the content true or false, when you make your change.
With an option like that it would be much easier to play around with templates and make changes seamless without any boundaries or risking loosing your created content by mistake.