Decide what to do with Source eslint-plugins storybook READMEs and other Source stories

The eslint-plugins storybooks consist of just one story which is importing the project's README.

- Should these even be stories?
- Do we want to create AWS amplify projects for them if so?
- Or shall we just leave them as READMEs in the project?

There are also several other stories that pertain to Source generally that are currently all held together in the GH Pages storybook. As we are now splitting into a Storybook per package, we need to decide where these stories will sit.

Should we thus have a Source 'documentation' Storybook?

Should this also contain the Eslint plugin docs? Or should these be their own Storybook as they are packages (but only one README)? Do these have to be in AWS Amplify or can we keep using GH pages?

Should we keep separate package Storybooks for Foundations, Components and Dev Kitchen, or does it make sense to compose them all back into one large Storybook again (and include the docs above)?

About the packages - could these move into their individual Storybooks?:

Contributing to Source - this pertains to all the packages:

Release notes (out of date - we now have separate versions for each package) - should we scrap or add to each package?: