"Extending Twine" suggestion: option to use Tabler icons for toolbar buttons instead of having to supply icons oneself

[webbedspace]

I feel like most story format toolbars will generally need the same kinds of symbols: bold, italic, hyperlink, borders, colours, alignment, columns, etc. It would be convenient if the same icon library that Twine uses was made available to story formats. I envision specifying icon-tabler-, and a suffix, for the "icon" property, in place of a URI.

Tabler has an icon font .woff which can be included, even if the Twine UI only uses its transcluded SVGs.

[klembot]

I get why this is an appealing idea. This is another place I was trying to keep Twine and story format extensions less tightly coupled, as I could imagine a lot of gnashing of teeth if the Font Awesome dep had been exposed to formats in the past and I switched to Tabler (there are many overlaps between the two, but it's not a one-to-one). A couple considerations...

• I consider icon fonts no longer best practice; we'd have to investigate load impact of the entire SVG for web users (not just file size but initial render time).
• People will inevitably request that the icon library be expanded, or submit their own, and then we'd have to grapple with whether we want to maintain our own subset of Tabler (my inclination would be no, it sounds like a can of worms).

From a practical standpoint, are there difficulties with adding the icons via NPM and including them during story format production? That was the strategy I was planning to use with Chapbook.