Diego, I agree with the idea, searching for and discovering plugins is a complicated process at the moment. However, instead of finding a new interface, why not use the existing ones? I don't know the Javascript / NPM world enough, but I have the feeling that we could use NPM to distribute Tiddly plugins. If all plugin makers would follow the same schema and register (?) his/her plugin to the NPM registry, it would be easy to update, search, and filter the plugins. The downside of this is that it only works with directory based wiki, not with single HTML.
In order to achieve uniformity, I am working on a plugin edition where all the necessary files are available to create a new plugin, all you have to do is change the appropriate fields (this could be automated later). At the moment, *it is not yet working, don't use anyone*, but the idea I hope is understandable. https://gitlab.com/bimlas/tw5-plugin-template/ -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/99f3a88c-92f8-41c0-bf09-119b040f4836%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
