But here comes Drupal SDC, the hungry newcomer, and it’s already slipping Storybook’s jab. With SDC, you don’t have to wrestle with multiple YAML variations spread across your project. Instead, by utilising the contributed Drupal module SDC – Component library you can instead write *.story.twig files, placing the preview definition right next to your component with no context switching and no hunting around. Want to show your component in different wrappers, or drop it into a specific page-like scenario? Easy. Just write it in Twig, the same language you’re already using to build your site.Scorecard: Storybook 9 | Drupal SDC 10That native integration is a big deal. With Storybook, if you want to tweak the layout of your previews, you often find yourself tinkering with Storybook’s own React-based plumbing which can feel like stepping into another weight class. With SDC, you stay in Drupal’s corner, fighting on familiar ground, and that makes your workflow leaner, faster, and more intuitive.The judges tally up the first round. It’s close! Storybook’s experience and ecosystem show through, but Drupal SDC lands the cleaner shots where it counts: simplicity, flexibility, and staying native.The bell rings and the fighters come out swinging. Right from the start, Storybook shows us why it’s been the reigning champ for so long. Its workflow is powerful, flexible, and familiar to frontend developers across the globe. You define variations of your components through structured YAML files and javascript / react stories, giving you a reliable way to showcase every state of a button, a card, or a complex widget. Once you’ve invested in the setup, you’ve got a polished arena for your components to dance under the bright lights.
