Hi folks,
Thanks for bringing up these issues again! We’re currently working together behind the scenes on how to address your questions and concerns. We realise this is taking longer than expected — Atlaskit is an umbrella for the work of multiple teams at Atlassian, and we’re trying to paint you a full picture. Thanks for your patience!
We are collating all your questions and will post a new FAQ once we have the answers. We’ll keep that updated over time. We want to make sure we’re not missing anything, so two questions for you too:
- Which components specifically do you rely on?
- In addition to npm packages, how do you currently consume them?
Quick updates to the more straightforward bits:
- We’ve heard your feedback about how moving the repository to GitHub needs to be carefully considered. We’re putting the move on hold, and will continue updating the existing mirror repo on Bitbucket.
- It was an oversight that the Navigation components (horizontal and side navigation) were left out of the mirror repo since they are in a separate /navigation folder. We’ll add them. You can upgrade to them and rely on them.
- Good news on the license changes for icons! We just received confirmation that we are able to change the license to Apache 2.0. This will all be official shortly, once we update the license in the repo itself.
- The “What’s next?” section above covers new items on the Design System roadmap since I last wrote about what we’re focused on. The docs website mentioned is the newly-launched atlassian.design, and the per-component performance improvement work is still our top priority right now. That will continue for many months to come.
Again, we hear that you have questions about private vs. public components, how we share the code, etc. We will address those. The underlying investment in Atlaskit and the Atlassian Design System that we wrote about a few months ago continues unchanged — it’s not going away!
Cheers,
Stephen