obsidian

Vault structure in Obsidian follows best practices for organizing notes, metadata, and configurations. Use folder hierarchies aligned with your knowledge domains, configure vault settings for sync and plugins, and establish naming conventions for consistent retrieval and linking across your notes.

Obsidian URI automation enables external tools to trigger actions within your vault—creating notes, opening files, executing commands. URI schemes accept parameters for vault selection, file paths, and content, allowing seamless integration between Obsidian and scripts or external applications.

Plugin development uses TypeScript templates and Obsidian's API—App, Vault, Workspace, MetadataCache, and FileManager—to extend functionality. Create a plugin skeleton, register commands or event listeners via lifecycle hooks, bundle with npm, and load into your vault for custom workflows.

URI schemes trigger actions from external applications into Obsidian; Local REST API provides programmatic read/write access to vault data via HTTP endpoints. Choose URI schemes for external automation or Local REST API when you need bidirectional data integration with external services.

Markdown extensions in Obsidian plugins use the Markdown post-processor or custom rendering libraries to parse and display additional syntax. Plugins can register renderers for custom code blocks, add inline formatting, or transform markdown during note processing.

Yes, Obsidian plugins require TypeScript. The plugin template and API documentation provide scaffolding and examples; TypeScript knowledge lets you define types for vault data, event handlers, and UI components needed for plugin development.