vault-structure

Obsidian vault structure should include dedicated folders for notes, attachments, and templates, plus a .obsidian config directory. Organize by project or topic, use consistent naming conventions, and version-control core config files like app.json and workspace.json to keep team setups synchronized.

Store templates in a dedicated templates folder within your vault, and manage core configs (app.json, workspace.json) in the .obsidian directory. This separation makes templates reusable across notes and keeps configuration changes trackable for team environments.

Yes. Templates stored in a standard vault structure can be referenced and reused across workspaces by maintaining consistent folder paths and exporting template configurations. Team collaboration benefits when template folders and workspace.json settings are shared via version control.

Designate a dedicated attachments folder within your vault root to centralize media assets. Reference this folder consistently in your app.json configuration so all notes link to attachments predictably, reducing broken links and improving collaboration.

Use a shared vault layout with clear folders for notes by category or project, standardized templates for consistency, and checked-in .obsidian config files. Document folder purpose and naming rules so team members follow the same structure.