Would it be a good idea to have a template plugin setup and maintained alongside the existing list of plugins?
I was trying to think of a way to make it easier for develops to setup a new plugin and thought it might be easier to just copy and paste an existing plugin class library and just make the changes necessary to get started.
It could be named something like "Nop.Plugin.GROUP.NAME.Template" for example.
It could have most of the .csproj file setup but with parts commented out (so as not to copy the plugin to the directory along with the others) and include placeholders for information that needs to be included.
It could have a plugin.json file included with sensible defaults.
It could have a Plugin class (perhaps).
It could include any other (empty?) folders if you wish to encourage a sensible default structure amougst plugins.
It could (probably should) include a readme.txt with instructions of how to copy it and set it up as a new plugin.
Anyway, just a thought.