Separate re-use from organization.
Ignore this one. Just a vague thought I need to expand upon later.
Collections pull double duty as both a tool for re-using things and for organizing things whether or not they will be re-used.
To keep such things separate I add a $ to the names of collections intended for reuse as collection instances. This has the added benefit of floating such collections to the top of the "add collection instance" list.
Similarly, groups in the material editor and geometry node editor pull double duty as both a tool for re-using things and for organizing things. The dozens of groups I made just to make the node networks easier to read make it painful to find the 1 node group in my file that I need to re-use.
There need to be intended for reuse entities in the system that are separate from the organization helper entities.
2 Comments
Restricion toggles by names and RegExr in outliner
Maybe collection can be "instanced depthly"? blender.community/c/rightclickselect/WPqg/
I see still fighting the "component" issue : ) It's crushing me every-time. I dreaming to edit linked collections/objects in external file loaded to "Base" as some "immersion effect".
After time with work groups from other scene I see the problem with position of these objects, collections, etc. Also blender still is poor here.
I'm using
__coz is more friendly for python script BPY, etc. and__1_All is possible, but BF prioritizes are different.