This repository was archived by the owner on Jan 6, 2025. It is now read-only.
Remove storybook and replace with codesandbox
#460
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to relevant issue
This pull request resolves #446
Description of changes
Remove Storybook and replace it with CodeSandbox sample links.
Context
While Storybook was originally used for both testing and documentation it is now exclusively used as a sort of interactive component sandbox that is used to augment our documentation.
Due to a recent PR, Storybook can no longer be built with no easy fix and the CD pipeline for deploying Storybook has been removed as a result.
This means the interactive components are still available but new releases cannot be made, and as time continues the docs are at risk of becoming out of date. As a result, we transitioned to using CodeSandbox for achieving interactive component demos/samples.
In the further future, we may end up using GitHub Blocks to enable interactive demos and static doc content to live side by side in the same markdown file.