You can duplicate your Projects to quickly adapt existing content. This can help you to work quickly and efficiently when creating elearning at scale. However, we recommend following duplication best practices to help you get the most out of this feature and avoid things like legacy edit build-up which can cause slower load times.
Always duplicate from a central template
Set up a Project that all authors can duplicate from as a starting point. You could set up a folder in your account that all authors can access and duplicate from.
Working in this way will ensure that the duplicated Projects don't have large amounts of legacy changes saved in the database. It can also mitigate the perpetuation of any issues that become present in the copies and make them easier to track down. For instance, if an issue is present in the original Project, then it is easier to find the origin versus if an issue from a copy is duplicated into others.
Avoid chaining Project duplicates
Try to avoid duplicating from a previously duplicated project
Don't create a chain of duplicated projects as it is possible that this could have an impact on loading time as legacy edits build up over time.