Jay OK, if it’s like you say then it truly is just a change “under the hood” and I have no complaint.
I like your suggestion for grouping all auto-fill contents (tags, Move-to, etc.), with one exception: I like the way #tags are currently compartmentalized by document because it acts like a sort of “data validation” feature. I’m less likely to typo a tag or accidentally use one that doesn’t “belong” in that Document. It’s imperfect (because I can still manually type any tag, even a new one) – but it’s 98% effective. Your grouping proposal would be less effective. Perhaps you could modify it so the heading for the out-of-“document” tags group is shown but not its contents – user must click the heading to expand it. Or, handle this more robustly with a Tag Manager feature, which is sounding more and more needed as Legend evolves. For example, the “other documents” tag group could be disabled entirely for a shared document.
It sounds like in the new version “Document” will just be shorthand for “Root level Parent”, and presumably there will not be root-level ITEMS…or will there? Seems troublesome. Either way, I suggest keeping the user-facing “separate documents” paradigm as it is now.
