Consolidation of Plugin(s) use of Icon Packs with Core leading the way

Feature requests
1

Use case or problem

I am using some of the best plugins in the world and many of them are using some sort of Icon packs. Each plugin does this for themself and this causes a large explosion in size of my vault(s) due to repetition of the same icon in multiple locations. Some, but not all are:

  • Obisidan Icons
  • Obsidian Icon Shortcodes
  • Obsidian Icon Folder
  • Obsidian Admonitions

Proposed solution

Would it be possible that Obsidian Core allows the user to use either the current built-in Lucide icons (as it does today) or move these into a special directory under the .obsidian folder. Then other projects could also use this directory for their icons.

Additionally, I would ask that a official format be described by the Obsidian team so that there are not duplicates within the folder. For example, that the Icon Packs be in directories with a specific naming convention (lucide-dev, fontawsome-line, rpgawesome, etc.)

Lastly, would it be possible to allow this directory outside of a vault, so that multiple vaults could use one single icon pack database (moving from .obsidian/icons to ../icons. The use case would be that I have multiple vaults in an overarching directory:

Option 1 (no global icon-pack folder):

./Notes
├── Vault A
│   ├── .obsidian
│   │   └── icons
│   │       ├── lucide-dev
│   │       └── font-awesome-brands
├── Vault B
│   ├── .obsidian
│   │   └── icons
│   │       ├── lucide-dev
│   │       └── font-awesome-brands
└── Vault C
    └── .obsidian
        └── icons
            ├── lucide-dev
            └── font-awesome-brands

Improved Option with global folder:

./Notes
├── icon-packs
│   ├── lucide-dev
│   └── font-awesome-brands
├── Vault A
│   ├── .obsidian
├── Vault B
│   ├── .obsidian
└── Vault C
    └── .obsidian

Current workaround (optional)

I have no current workaround.|

Related feature requests (optional)

I have found no other requests of the sort.

1 Like