Storybook Integration: resolves #24

[DanielMiller-agile6]

Integrated Storybook so we can experiment and discuss how we might use it for maintenance, design, and development tasks. I only wrote stories for existing reusable components (files under /src/components), along with an additional one to document the site's color palette.

I also removed the package-lock.json file since this isn't used with yarn and can lead to errors for developers and builds. The yarn.lock file has been updated to account for new storybook dependencies.

This PR doesn't change any public-facing site content.

Resolves #24

[netlify]

Deploy preview for agile6 ready!

Built with commit 8abb810

https://deploy-preview-27--agile6.netlify.com

[netlify]

Deploy preview for agile6 ready!

Built with commit 0461b91

https://deploy-preview-27--agile6.netlify.com

[ElijahLynn]

Is this something we can route to /storybook?

[DanielMiller-agile6]

@ElijahLynn That should be possible. You mean as a github-pages site or a route on agile6.com? I still need to work out some scripts for static builds, but it's mostly working i think... I can work on that in a follow up PR. The main gotcha here is how Gatsby compiles static GQL queries separately from storybook build scripts, so in order to publish storybook as a static site, we also need to build the Gatsby site first so that assets from /public are available.

[ElijahLynn]

@ElijahLynn That should be possible. You mean as a github-pages site or a route on agile6.com? I still need to work out some scripts for static builds, but it's mostly working i think... I'll can work on that in a follow up PR. The main gotcha here is how Gatsby compiles static GQL queries separately from storybook build scripts, so in order to publish storybook as a static site, we also need to build the Gatsby site first so that assets from /public are available.

Yeah, I mean as a GJS route. I'll play with this locally soon. Thanks.