∞
@AndySylvester @help As an alternative, you could expose the glossary data as a JSON field setting instead of a file. That way, people using your plug-in can just hit the Settings button and edit the glossary data directly, like this:
I am an aspiring world's best uncle, co-conspirator with Sanna, and curious coder based in Jönköping, Sweden. If you spot someone hiking deep into the forest of Tiveden, that's probably me. 🌲
@AndySylvester @help As an alternative, you could expose the glossary data as a JSON field setting instead of a file. That way, people using your plug-in can just hit the Settings button and edit the glossary data directly, like this: