@AndySylvester @help As an alternative, you could expose the glossary data as a [JSON field setting](https://help.micro.blog/t/plug-ins/104) 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: ![Screenshot of a text area with the label Glossary JSON and example JSON data filled in. There are two buttons: Back and Update Settings.](https://dahlstrand.net/images/glossary-json-field-example.png)

AndySylvester

@help @manton @sod I have created a new plugin which uses a JSON file that the plugin user needs to edit. How do I indicate that this file exists and provide a way to edit? Is it the includes element in plugin.json?

2023-03-07 20:36

Embed

In reply to

sod

@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:

Screenshot of a text area with the label Glossary JSON and example JSON data filled in. There are two buttons: Back and Update Settings.

2023-03-11 08:46

Embed

Micro.blog

Micro.blog