Globals are a great way to quickly update the site. I use them a lot. It would be helpful if you could organize them into folders to keep things organized.
3 Likes
How would you see this working?? The globals for the project are already listed in the component view for the project.
If you use a lot of globals, the list could become very long. A way to organise them is one way or an other ( for example in collapsible folders) it could help.
I’d prefer that globals had their own panel on the left; pages, resources, components, and globals, as while they are made of elements/components they really are site specific, whereas the standard and 3rd party components are available in all sites/projects - globally if you will. 
As it stands having them all in the same tab is a little confusing. Having them in a separate tab where you can organize them into groups, folders, etc. would be really helpful and create a better separation between the two different types of objects.
I tend to view the components as ‘the pantry’ (the ingredients you can use globally across all your projects) and the globals as ‘the pot’ (the stuff you’re using in your current project). It’s also the reason why I still think ‘globals’ for objects that are local to your site is a confusing name/concept.
1 Like
I like this idea a lot.
Especially, if eventually there could be some option that allowed you to export the collection of globals for use in other projects.
3 Likes
But wouldn’t that be more apt for say, a custom component, as opposed to a global…I am not quite seeing that.
I can definitely see a custom component being used across projects. I am not seeing that for a global which would be used across pages within the same project.
I also concede that I might be missing something…
This would be less useful now that Elements supports dragging a global from one project to another. But if there are a collection of common globals it would be nice to export them together and then load them into the globals section of a different project. I have created a large number of globals that handle certain functions on my sites, for example, my own take on the now defunct Card component. I use these on all my sites, so I was just thinking of ease of use.
This is an interesting idea, and one I think might work. I’ll add it to our ticket list!
1 Like