metadata corrections

[jonschlinkert]

There is a difference between how a plugin should be named and keywords. Keywords, if we're going to match by them, by necessity should be as close to fail proof as possible. Plugin names should be readable.

I'm using assemble for obvious reasons, and assembleplugin for the same reason that Grunt standardized gruntplugin as the keyword that is used for identifying plugins that will show up on their website. assemblecollection is what I'm thinking of going with to indicate that it's a "contrib" plugin. which is what Grunt uses on grunt-contrib https://github.com/gruntjs/grunt-contrib/blob/master/package.json#L62, https://github.com/gruntjs/grunt/blob/master/lib/grunt/task.js#L378

[jonschlinkert]

so I think:

• "assemble-plugin" for plugin names
• "assembleplugin" in the keywords, but you can add whatever additional keywords you want
• "assemblecollection" for "contrib" plugins that might be bundled together like grunt-contrib for anyone who wants that.

Same pattern for helpers I think. Btw, fwiw my background is analytics and SEO, so I'm trying to keep that in mind too

[AndersDJohnson]

Nice, I guess you've thought it through thoroughly. And I am in agreement.

I've updated my two published plugins to reflect these conventions, both on GitHub and in npm.

• adjohnson916/assemble-plugin-related-pages
• adjohnson916/assemble-plugin-markdown-data

[jonschlinkert]

awesome! thanks, keep up the great work!