@jsyip , thanks for your guidance, but your statement is not true. In fact, at least 1/2 of the old design guidelines are not present on the new site. The old site remains the only way to find these guidelines.
Some of the omissions in the new site are striking. For instance, although the new site had user guidelines for the “Pagination” component, the new site doesn’t include the “DynamicTable” component, much less the user guidelines for the DynamicTable, a component without which a Pagination component on is an orphan.
Nor does the new site have the “Form” component (a lynchpin of any design system) or that component’s user guidelines. Similarly, it’s missing all layout related components, all date/time related components, and all navigation components.
IMO, @remie hits the nail on the head: the main problem with the new site, along with Atlassian’s decision to disable real-world usage of the source code (a successful
yarn install for any of the “public” components hasn’t been possible since 2019) means that Atlaskit no longer serves the more deeply committed app developers and integrators that have spent years working with these components. To this audience, the old site remains the only alternative for documentation. So, if you don’t intend to invest in it, hopefully it won’t follow the path of the Atlaskit source code to non-public access.
Atlaskit used to be a complete solution for, as @remie says, delivering consistent in-app experiences to enterprise customers. With full source and build system built in, it could pass security review and be integrated into an enterprise pipeline. But not any longer.