We often recommend using themes or building modules over cloning individual assets, this article will dive in a little deeper into why we do this and things to keep in mind when cloning assets with Knak.
Cloning makes it harder to manage content
If users always build from themes or build from modules they always start with the latest, most update to date content. If you clone there's a high change some of the modules will be out of date, meaning the you may end up using out of date content or would have to update them all to the latest version.
Cloning an asset/module copies over everything
This includes alternate text, links, and anything else you customized in that particular asset/module will carry over. If you consistently clone everything, you are more likely to forget to update something important.
Themes are better at promoting a cohesive look for your brand
Themes are easier to control from a brand perspective. For example, themes can be created and then specifically deployed to brands with certain restrictions, whereas you lose some of that functionality with cloning emails. Themes & modules can always be unpublished or unassigned from a certain brand, but if you use a cloned asset those outdated modules would still be there.
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com