Best Practices for Structuring and Managing Diagrams, Templates, and Collections in LeanIX

Hi LeanIX Community,

We are trying to establish an enterprise-wide standard for organizing diagrams and architectural documentation in LeanIX. Our goal is to bring consistency and avoid duplication, especially where a single application supports multiple business capabilities.

We are looking for guidance in the following areas:

1. Naming conventions:
   What naming standards do you use for diagrams to ensure uniformity across domains, capabilities, and applications?

2. Folder/collection structure:
   Since LeanIX doesn't have traditional folders, what is the recommended way to structure Collections for domains, capabilities, and applications?
   Is there an industry-standard approach for ensuring that each application has a single authoritative home?

3. Classification metadata:
   Do you primarily use tags to classify diagram types, maturity, and architecture states (current/future), or are there better methods?

4. Managing collections & avoiding duplication:
   How do you handle cases where applications support multiple capabilities without scattering diagrams across multiple collections?

5. Reuse of templates and stencils:
   How do you centrally store and manage reusable templates, legends, and stencils so that architects across teams can maintain consistency?

Any examples, screenshots, or governance frameworks from your organization would be extremely valuable.
Thanks in advance for your advice!