As the library grows in API size, it becomes more difficult to read about the available options on the repository README. Ideally this library should have a seperate website for documentation, with separate pages for each option and live intractable examples, same as the React Flow docs. They mentioned in their blog post that they're using Docusaurus, will need to check it out.
Ideally the documentation should be all statically build, and I should be able to deploy it using gh-pages, to save on server and domain costs. The current GitHub page hosts the Storybook examples and tests, but they can be moved to a free tier on Chromatic.
As the library grows in API size, it becomes more difficult to read about the available options on the repository README. Ideally this library should have a seperate website for documentation, with separate pages for each option and live intractable examples, same as the React Flow docs. They mentioned in their blog post that they're using Docusaurus, will need to check it out.
Ideally the documentation should be all statically build, and I should be able to deploy it using
gh-pages, to save on server and domain costs. The current GitHub page hosts the Storybook examples and tests, but they can be moved to a free tier on Chromatic.