Consider unifying Storybook and docs

[dzucconi]

The experience of trying to update the palette-docs is frustrating. No types, every change seems to trigger errors on compilation, changes randomly pop up the "Gatsby.js development 404 page" etc. All its dependencies are out of date and it's difficult to manage installs in palette from the root because installation of docs breaks. Most of the information surrounding process is no longer relevant, etc, etc.

One option we have here is to just upgrade to the new Story format and either write a custom wrapper that utilizes the exported stories, or just use Storybook + mdx docs to improve documentation from within storybook.

[damassi]

The experience of trying to update the palette-docs is frustrating. No types, every change seems to trigger errors on compilation, changes randomly pop up the "Gatsby.js development 404 page"

Maybe we should pair? The team has been working in these docs since 2019 with none of the problems that you've mentioned here. It's quite possible you're boothing things incorrectly, or misunderstand something in the toolchain.

That being said, storybooks does have a nice MDX feature now, and it would simplify things.

[damassi]

Pulling palette repo down, i noticed that common fsevents issue. Regenerated the lock file and yarn install --check-files and things installled as expected. yarn start then booted the docs as expected. Changes to palette are then picked up by gatsby.