To get an account, and have access to use Bit's @carlsberggroup scope from your project, please request access here.
To access Malty in Bit.dev cloud, you can head to https://bit.dev/carlsberggroup/malty
Yes, both to use Bit's CLI to import and consume Malty components, but also to create components, or submit changes to existing ones, as Maintainers. For instructions on how to install Bit locally, and understand its dependencies, please go here.
Yes, and no. Yes, they overlap in functionality on the documentation side of things, but they also differ in our use of Bit. We are only using Bit as a packaging and distribution solution for our Malty Component Library; that's it. We are not using Bit for documentation purposes.
The main reason for this is simple: ZeroHeight integrates directly with Storybook, and not with Bit. Also, at least at the time of this writing, Storybook provides a superior documentation experience, both for authoring, and UX.
As a Consumer you don't, all you need to do is import components directly into your product.
As a Contributor or Maintainer, you will. As a Contributor, you will need it mainly to open the PR, but all the work prior to opening the PR can actually take place on the cloned repo; running Bit and Storybook locally. For more on this contribution flow, here.
The million-dollar question! ... head here.
The Component Library is the core of Malty on the Dev side. It’s the equivalent of the Figma assets on the Design side.
It’s a GitHub-hosted mono-repo, but it never needs to be run locally for Consumers. Contributors and Maintainers will need it to manage to pull requests and make broader changes to the mono-repo itself.
Of course, you can! Although this must be in coordination with Malty Maintainers. Open a ticket on our Service Desk, and reach out through Teams.
There are a couple of different paths to making changes to a component, and those paths depend on the scope of the change. Let's connect!
We will do everything in our power for PRs to be approved as fast as possible. But it mostly depends on the bandwidth, workload, and how much help we get from the Product teams. Ideally, not long.
To be fully transparent the process itself takes minutes, but reviewing can be where the bottleneck is.
As Devs we are at the end of the line — for better or worse; you have to push your team to understand that. Your product being Malty's compliant means:
- You never start from scratch, you have Component Library to work with
- You have a community to support your development. They’re all using the same components!
- You never have to worry about CSS or Design specifics
- You have DRY code within your codebase, 100%!