-
-
Notifications
You must be signed in to change notification settings - Fork 540
Description
What problem will this feature address?
Docs projects have become a staple in modern monorepos, and continue to have a growing focus on outstanding UI aesthetics.
A current pain point with the UI components documentation experience in Fumadocs is the ability to quickly experiment with and view various states of the components.
Describe the solution you'd like
I've already shipped storybooks containing Fumadocs UI components to production, here's an example.
The ability to quickly change the state of a component and see the code has been an enormous boost to developer experience. It makes the components self-documenting, and eases onboarding greatly to open-source project by lowering the 'finding UI components' curve in the codebase.
I was an early adopter of Fumadocs, and realized its potential very quickly. Here's one of my early projects where I made the attempt to bring this vision together.
Describe alternatives you've considered
The following alternatives exist...
| Histoire | StoryLite | Astrobook | React Cosmos |
|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
and can be added as examples in the future as well. The goal would ideally be to leverage the Component Story Format - CSF as much as possible to avoid the maintenance burden.
Additional context
No response



