Unfortunately, what a feature is called does matter as it often provides users with an initial mental model from which to build their understanding of a feature/product and how it might be utilized. Metaphor is often also used to help create associations with other concepts designers wish to relate to a feature (ie. desktop, folder, templates, menus, clouds, etc) to further develop a users’ mental model.
You can often flush out possible names by describing the feature in text, much as you would in documentation, product marketing, or presentations.
What do globals do?
What benefits do globals provide users?
How are globals best utilized?
From my understanding, globals provide a means for users to create reusable templates that can then be combined to create complex layouts that can easily be managed across an entire site.
Globals provide users with personally meaningful templated regions of a page or layout. These can be as small as a piece of text, or as big as a full page layout combining additional templates and regions that can easily be modified, reused, and updated across a site.
Globals are best utilized by thinking about the behaviour, pattern or utility required of the templated region. For example; page headers, footers, menus, galleries, hero images, carousels, strap lines, descriptions, etc.
For me, ‘template’ is the word that keeps coming to mind. ‘Layout’ is too ambiguous, ‘element’ is easily confused with other elements, ‘component’ is possibly inferring more than they are, ‘fragment’ isn’t bad, but I fear it has baggage, and ‘global’ doesn’t really communicate much to the user (unless they’re a programmer) IMHO.