Hello everyone,
Following our recent preview release of Forge UI Kit 2, I’m excited to announce that UI Kit 2 is now generally available.
With this release, UI Kit 2 has been promoted as latest version of UI Kit and will now be referred to as simply UI Kit.
For more detailed information on using UI Kit components to design and build apps, please refer to our UI Kit components documentation.
We’re looking forward to seeing the amazing applications you’ll build with UI Kit. As always, we’re here to support you and welcome your feedback. Please feel free to comment on this post with any questions or thoughts you have.
Best regards,
Jemma
14 Likes
AUI: @atlassian/aui
Atlaskit: @atlaskit/*
Custom UI: more confusion.
UI Kit: @forge/ui before ~June 2023.
UI Kit 1: @forge/ui after ~June 2023.
UI Kit 2: @forge/react v9 and below.
UI Kit: @forge/react v10 and above, after ~April 2024.
GA release is awesome, thankyou. But the naming disaster here is going to cause much confusion and have cascading negative effects on the ecosystem. Every UI Kit forum post prior to today will now serve as a hostile artefact that wastes developer time.
3 Likes
Thank you for bringing this to our attention. We understand that the naming changes for the UI Kits can initially be confusing. We’ve made efforts to minimise this confusion by providing detailed documentation and callouts to guide developers through these changes.
We acknowledge that this is a valid short-term issue and we are actively working on a solution to streamline the understanding of our UI offerings in the future and hope this will be a step in the right direction.
Regarding the concern about outdated CDAC posts, it’s important to note that technology and software development are fields that evolve rapidly. As such, older posts naturally become outdated over time as new updates and changes are implemented. We recommend developers to always refer to the most recent documentation and announcements for the most accurate and up-to-date information.
2 Likes
I’d be thinking about the forums as ~50% of your documentation strategy. Every post and every search on the forum happens because the docs are inadequate in some way. This is why the forum exists.
The naming decision would be fine if the underlying package were the same. @forge/ui and @forge/react are separate incompatible packages.
When developers now search the forums, the name “UI Kit” will apply to both packages depending on the date of the post.