My company is thinking about using Storybook to manage our front-end components. And since there is a UXPin-Integration, it would benefit the product design workflow as well.

But now I'm asking myself, how the new workflow could look like? As far as I understand the Storybook-Integration, you're just able to drag the Storybook-Components into the UXPin prototype and change some attributes which are setup inside the component. But you're not able to alter the design like you're able with UXPin-Only Components, right?

With my current understanding, an example workflow could look like the following:

  1. I create the UXPin-Protoype like I usually do. I usually already setup the UXPin-Components in the atomic design way.
  2. The dev's are starting to implement the design into their components and fill up the Storybook components.
  3. As soon as the developed Storybook-Components are testet and agreed by the customer, I integrate Storybook into UXPin and I'm starting to replace "hand-made" UXPin-Components with the Storybook-Components.

If after some time into the project, we have to design new components, the process is going to be the same: I design it in UXPin, the devs are developing based on UXPin and push it into Storybook, i pull it from storybook and replace my design?

So the only benefit is, that the UXPin-Prototype stays up-to-date without me having to adjust every change that's done in the frontend? Or am I missing something?

Or do you have a better way to implement Storybook into your workflow?