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
This looks like a cool service but I'm not sure how comfortable I am with reusing the branding of an open-source project for a paid product?
I know the MIT license enables commercial use (at least for the code – I'm really not sure how it applies to the Storybook name and/or logo) but my gut feeling is that I'd be more comfortable if the product didn't have "Storybook" in its name or reused the same icon.
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?
Well in the case of "LottieFiles", "Lottie" is a qualifier for "Files", so it's a bit clearer that it's a site built around the Lottie ecosystem: "Files for Lotties".
"StorybookForTeams" though makes it sound much more like an "official" project since "Storybook" is the main noun in the construct.
For example, do you see no difference between "HaikuFiles.com" and "HaikuForTeams.com"?
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. 
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.
 The raison d'être of open source is the ability to belong to no one. That includes the notion of "officialness" — see "Linux"!
What I meant is that "Storybook for Teams" makes it sound like a product put out by an entity or company called "Storybook". So to me it's a bit misleading and goes against that "open source belongs to no one" philosophy.
I would have no problem with a product called "Classroom – Storybook for Teams" for example. I just find that piggy-backing on an established open-source product's brand and reputation so closely is a bit of a grey area for me.
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.
lol, I still don't think you get what he means...
He's saying that it sounds like you folks are from Storybook. When in reality you are not affiliated in any way -- which is obviously misleading to the consumer.
At first, I thought this product is by Chroma (the core maintainers).
I’ m agree! this totally misleading to the customer.
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.
Hey Dominic from Chroma here. I designed the Storybook UI, brand, website, and work on the design system.
Our team recently learned of this project. Our focus is building Storybook, as we have for 3 years now, and supporting customers of our visual testing tool Chromatic. We're not here for drama and haven't "sown" a thing.
Please leave us out of it ✌️
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.
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.
ok i'll bite. what's storybook?
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.
No need to bite, Storybook is a big deal in the front-end engineering world. I don’t think they meant to bait you.
I was interested until I learned this was built by the Haiku team
Looks like very useful tool, I am evaluating it. Cool!