Hey Dominic — mad respect to you, Chroma, Zol, and all of the work you've done contributing to the Storybook community.

I stand by the belief that any narrative of ownership between Chroma <> Storybook is harmful to the ideals open source. The "if-statement" above is far from an accusation.

Dominic, please speak up if you feel like Storybook for Teams is in poor form vis-a-vis the Storybook community! As a fellow career open-source contributor, don't you share the sentiment that it's good for Storybook that we're helping democratize access to the tool and helping spread awareness?

We are open to renaming the product.

Chroma has hired many of the Storybook contributors and has taken over the maillist, discord, etc. They've injected themselves as benevolent corporate overlords of the open-source project.

Others have expressed alarm over Chroma's actions and intentions: https://medium.com/protecting-storybooks-future/storybook-is-being-commercially-hijacked-463524825fbc

Your implicit sentiment that Storybook belongs to Chroma seems to validate some of the concerns of that author. If anyone is sowing a narrative of "owning Storybook" — well, I'd recommend double-checking where the "misleading" is coming from.

What does it mean to be "from Storybook?"

Is Red Hat Linux part of the Linux community? What about "Linux for Dummies?"

My point is: Storybook is a community. Anyone can be part of an open-source community, but we're also contributing value to it! By democratizing Storybook. Storybook for Teams is Storybook.

Just like Storybook Native will be Storybook.

I believe I understand your position — "x for y" makes a bold claim on x. Is it leeching off of x, or is it propping it up? Where's the razor?

We are seeking to provide value to the Storybook ecosystem via democratizing access to the tool. We come into it understanding that there's not a centralized owner for the community, and that "everyone is free to contribute."

This is an initial beta-launch though, and we are quite open to feedback & learning — and we are open to renaming this product if our understanding doesn't mesh with the community's.

Storybook for Teams is an official project. It's built & maintained by Haiku (officially,) and we're doing our darndest to provide (official) value to the ecosystem. [1]

LottieFiles is official in exactly the same way. GitHub is official too.

Worth communicating: S4T isn't Haiku's first contribution to the design systems ecosystem — see diez.org. It also won't be our last. We have designs laid out for "Storybook Native," for example.

[1] The raison d'être of open source is the ability to belong to no one. That includes the notion of "officialness" — see "Linux"!

Hey Sacha, thanks for this feedback

To better understand where you're coming from: do you feel the same sentiment re: lottiefiles.com?

Motion designers & developers have strongly positive associations with LottieFiles, from what we've seen via Haiku Animator.

LottieFiles is commercial — AND it makes users' lives better. It builds on the Lottie open-source brand and enhances its ecosystem.

That's exactly our goal with Storybook for Teams. Do you feel like we're missing that mark?

Storybook is an open-source developer tool for visualizing & developing web UI components in isolation, without having to fire up a whole codebase. https://storybook.js.org/

Over the last few years it has gained a ton of adoption, especially in enterprise design systems where folks are focused on bringing designers, developers, and product teams into closer collaboration.

Storybook is great for designing & developing UIs, but it's only accessible to folks comfortable with the command-line, git, build-tools, etc.

Storybook for Teams makes it easy for anyone on your product team to join the party.

Built by the Haiku team as part of our mission to connect creators of software & empower new creativity.

Read more in the introductory blog post: https://medium.com/haiku-blog/introducing-storybook-for-teams-fdb89dd632f9

Hello fellow child-at-heart! :)

(Diez is the Spanish number 10, pronounced /'djes/, or "D S". Like "Design System.")

Hey Andrew, great feedback & questions!

1.) Since Diez just launched open-source, we need a bit of time before we land legit case-studies. That said, our beta-testers included teams from well known companies like Accenture, NBC/Universal, The Guardian, Cisco, Patreon, P&G, Atlassian, and McKinsey — we continue to work closely with several of these teams, and we're offering integration, support, and training as part of Diez Enterprise Edition.

In short, we'll be publishing case-studies as soon as we possibly can.

2.) To your specific questions "[1] Is it faster? [2] Will my engineers be able to comprehend it faster? [3] Does the Sketch integration auto-sync w prod/staging servers? [4] Can you show me?"

[1] Yes [2] Yes [3] No: if you want this functionality it needs to be set up by your developers; Diez offers the tools for DIY automation but no servers/services [4] Yes absolutely.

Fill out the form for Diez Enterprise Edition at the bottom of diez.org and I'll be in touch to schedule a call with your team.