Eleventy: Make plugin creation more structured to make discovery easier

[chrisdmacrae]

A lot of frameworks are now namespacing their plugins as a requirement, to make discovery easier and installation more magical.

E.g, gatsby requires:

• gatsby-source-*
• gatsby-transformer-*
• gatsby-plugin-*

etc

Parcel requires parcel-plugin-*.

I propose eleventy does the same thing, with eleventy-plugin-* or 11ty-plugin-*.

[chrisdmacrae]

@zachleat I'm going to draft an update to the plugins page detailing how to develop a bunch of different plugins.

I'll also pull in any found plugins on NPM and list them.

[zachleat]

Beautiful idea. I’d stick with exclusively using eleventy-plugin-* though if we can.

[Ryuno-Ki]

You could even ~steal~ copy ChaiJS' approach and list plugins automatically: https://github.com/chaijs/chaijs.github.io/issues/173#issuecomment-389127171

I looked around some more about how that scraping could be done and discovered npmsearch.

A query could look like https://npmsearch.com/query?q=eleventy-plugin&fields=keywords,name (for some reason, neither homepage nor repository returns a meaningful value.

I wouldn't expect problems if you don't jam their service … asking them is a nice gesture, though :-)

[Ryuno-Ki]

@zachleat Could you setup a 11ty/awesome-eleventy GitHub repo where we could PR plugins in?

[chrisdmacrae]

Heads up -- this is in the works, will try and push up a viable MVP asap.

[Ryuno-Ki]

@chrisdmacrae As stop-gap I went through npm and listed packages I found there.