Currently Templates are used to put in common scripts through Inline and External scripts modules by creating a fragment of them. Most of these scripts are required on each and every page of the website so it will be required to be added on each Template to make it available on pages of website.
It would be a great feature to have a single location where these common scripts can be added and anything that needs to be put on all pages of website could be added there. It can be a base template offering HTML Head, Body Begin and Body End slots which would get injected to all Templates/Pages of the website and an option to exclude this injection on Template/Page will allow flexibility.
This can help reduce the effort of adding/removing module/fragment to each template.
Thanks
Administrator
While this is an interesting idea, the time saved for inserting a fragment into templates would likely be minimal (as the number of templates for a site is typically not a large number). The ability to add or not add it is already there by design, and the efficiency of updating a fragment that is used in the typically moderate number of templates already allows a lot of efficiency to change this accross a site.
Also, our e-commerce SDK has the ability to create sitewide authorable 'app settings' that show up as authorable configs in Site Builder's Site Settings > Extensions interface. Using this you could theoretically extend or create a module (or multiple modules) that reads from this sitewide setting, allowing you to edit certain configs shared accross modules in a centralized fashion. App settings - Commerce | Dynamics 365 | Microsoft Learn
Thank you for your suggestion, and I hope the soutions above will suffice for the near future.