🧩 naming conventions for fish/fisher plugins

[DerekNonGeneric]

i noticed that jekyll plugins (and mostly themes) have defined naming conventions:

🔗 https://jekyllrb.com/docs/themes/#installing-a-theme

• jekyll- prefix for all jekyll plugins (perhaps postfix -plugin)
• jekyll-theme- prefix for theme plugins

Fisher plugins should probably also retain some convention (thoughts include):

• fisher-gap
• fisher-plugin-gap
• fisher-gap-plugin

maybe this would be our ideal name here (based on repo name):

• OpenINF/fisher-gap-plugin 🔗🐙

/cc @jorgebucaran

[DerekNonGeneric]

[…] all the same, Fish/Fisher plugins; Fisher uses Fish event system to trigger some install/update/remove events, but that’s about it. So, really, there is no such thing as a Fisher plugin — just a repo w/ functions dir and .fish files
— @jorgebucaran, creator of “Fisher”

[DerekNonGeneric]

hmm, the npm registry was untenable prior to scopes being added, which goes to show that having some naming guidelines seems preferable, and even if folks take the quote above at face value; i think the concept is much more well-defined than describing it as non-existent…