A lot of links to Component docs from https://atlaskit.atlassian.com link to the docs built from the pre-release “Atlaskit MK-2” (see link below). These pre-release docs lack a fair few important components (like Text Field). The repo proclaims itself as “… a spike of the potential new build system to be shared by Atlaskit, Media and Fabric.” I’m guessing linking to this is a mistake?
Since the UI looks identical, it’s really hard to figure out why core components have gone missing and I’m scared I’m reading docs for something other than I will get from npm.
We outgrew the architecture of our original repo, and rather than supporting 2 build systems in the same repo, we decided to build a new one and port things over. We’re nearly done (heading into the last sprint for it) and I apologise for the confusion in the current docs. I’d recommend just using the source code as the source of truth until the migration is complete. If a component’s src isn’t in Bitbucket then it hasn’t been migrated and will be in Bitbucket.
Again, we’re trying to minimise the confusion, but there are a lot of components to migrate across
Let me know if there’s anything in particular you need help with (or ping me on Twitter).
At the moment it doesn’t appear to be possible to raise issues against the new Bitbucket repo. Can you get that updated so I can provide some feedback on one of the new components?
Shall do. Glad to see you’re on this project. Loving your work. 