Make sure each plugin has an example

[hzoo]

cc @existentialism

everything in https://github.com/babel/babel.github.io/tree/master/docs/plugins

{% include package_readme.html %}

links to the readme in https://github.com/babel/babel/tree/master/packages such as https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-es2015-arrow-functions

Meaning make sure it has some kind of in/out example code + maybe a REPL link if it makes sense. Same with each option if it's helpful

We should also probably make sure the format of each readme is consistent (in/out, install, usage, options)

[lukyth]

I'm wondering what should we do if there's another information on a README in babel.github.io other than In/Out, Install, Usage, and Options.

For example, there is References on transform-object-rest-spread, should we move that section into the package's README (like babel/babel#4930) or should we just leave it on the website?

[hzoo]

References should be included if possible yes! If it's a transform it could link to the spec, or if it's a proposal link to that

[nitin42]

babel/babel#5393

[stale]

This issue has been automatically marked as stale because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions 👌!