Most organizations have libraries of prefabricated blocks for things like rails or commonly reused end conditions. The Template Library already supports drag and drop of one template into another using the Template Origin as the insertion point.

A needed enhancement is the ability to interact with these inserted templates as self-contained, linked blocks that can easily be modified or synchronized in place. If the original template is modified in the library, then the inserted form of that template in another is not also updated--there is no linkage. Usage of this template must be manually adjusted in every instance it has been inserted.

Additionally, in the case of multiple child templates being leveraged inside of one larger parent template using Display Rules, it is difficult to edit in place. Child templates need to be isolated from the parent when necessary for ease of modification. These child templates also need the ability to be manipulated as a single entity; this would allow for a modular hot-swap scenario wherein all associated points and components of a child template can easily be removed from a parent template if needed. The ability to treat these child templates as modular blocks would be a huge benefit in the creation and maintenance of "mega-templates" that are increasingly more common.

A further convenience would be to allow a child template to be created or dropped within the parent. A collection of points and components could be identified and grouped together as a child template and just as easily dropped if necessary.