Using an embedded URL is the quickest and simplest way to integrate DSM and Storybook. However, there are some instances where you may want DSM to host Storybook via the CLI-based integration. The following tables compares the methods and their respective advantages.
Embed a self-hosted Storybook URL in DSM.
This is the simplest and quickest way to integrate.
Upload your Storybook project for DSM to host.
Stories appear in DSM component pages based on a unique DSM page ID that you add to each story.
Supported Storybook version
No restrictions. If it appears in your self-hosted site, it’ll appear in DSM.
DSM may not immediately support new features that are introduced in Storybook.
No restrictions. Content that appears in your self-hosted site will appear in an iFrame in DSM.
DSM does not support stories written in MDX. It does support documentation written in MDX.
The theme appears as defined in the self-hosted project.
You can potentially maintain two different themes—one for the self-hosted project, and another for the DSM-hosted project. You'll need to apply the desired theme before publishing the project to DSM.
Versions are self-managed.
DSM keeps each version of a Storybook project that’s uploaded. Users can view different versions of a component.
Suitability for public documentation
It depends on the hosting details. If the self-hosted Storybook URL is behind a firewall, only users within the firewall can view the live component.
If the system is made public, any user can view the live component.