Make ready for npm public release

[raae]

Follow the info in this Gatsby article: https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/submit-to-plugin-library/.

I have to do the actual publishing, but you can get it all ready @olavea.

[raae]

The options available are described here https://github.com/raae/gatsby-plugin-fathom/blob/main/gatsby-plugin-fathom/gatsby-node.js and match the ones in the Fathom advanced docs: https://usefathom.com/support/tracking-advanced.

[raae]

You can see it in use on bottledhappines: https://github.com/raae/bottledhappiness/blob/master/gatsby-config.js (with .env variables) and raae.codes: https://github.com/raae/raae.codes/blob/main/gatsby-config.js (the most straightforward use).

[olavea]

• 1. Document Benedicte’s plugin with a README, using the contributing plugin template for reference.
• 2. Publish a package to npm (learn how on the npm docs).
• 3. Include the required files in Benedicte’s plugin code.
• 4. Include a keywords field in Benedicte’s plugin’s package.json

I have startewd with this @raae

1. Document Benedicte’s plugin with a README, using the contributing plugin template for reference.

https://community.bloggingfordevs.com/c/bi-weekly-blog/outline-jan-30-draft-feb-6-publish-feb-7#all_comments

[raae]

Do not publish to npm. I have already done so and will keep doing it, but since is missing docs and keyword it's almost like it's not there.

https://www.npmjs.com/package/@raae/gatsby-plugin-fathom

[raae]

How is it going @olavea, did you have something ready on your machine?

[olavea]

Yes, see these commits @raae

[raae]

Keywords looks good. Looking forward to the readme.