Hey folks,
Thanks for your patience so far! It’s been a busy time as we, like teams across Atlassian, work through plans for the new financial year (starting next month). I’ll have more to share about the Design System roadmap after that is finalised.
In the meantime, here are key pieces we’re working on right now…
Specifically with the community in mind:
-
Preparing to move our public repository (the mirror) from Bitbucket to GitHub, where it will be available alongside other Atlassian open-source projects
-
Renewed investigation into whether we can change the licensing for icons to a more permissive license
And across the Design System for everyone:
-
Performance — We’re focusing much of our energy on an under-the-hood performance pass of each component, refactoring them specifically with performance in mind. We’re looking to improve SSR rendering (time to render and size of output), first contentful paint, time to interactive, interaction response times, and of course, bundle sizes. Range, Avatar and Spinner are the first components to get this treatment, with AvatarGroup, Tooltip, Flag and Button next up.
-
Navigation — As you may have seen, there’s a new horizontal navigation experience that has rolled out across Jira and Confluence cloud. This is something that we’ve been working on over the past few months, and we’re now optimising its performance.
-
Docs website — We’re building a revamped website that will bring together design guidelines and code documentation (what’s on atlassian.design + Atlaskit websites), helping avoid any inconsistencies between them. We’re also reviewing the existing content to make sure it’s right.
-
Bugs in the queue — We’ve started a new push to go and smash through our admittedly large backlog of bugs and small improvements in the service desk queue. You may have already seen some older issues get dug up and addressed!
As always, I’m happy to jump in to any specific questions (also feel free to tag me in new threads about the Design System). And expect to hear more in July.
And for your question @naiara…
As part of the performance pass mentioned above, we will be removing (in due course) deprecated components including Field Base, where we can better optimise their alternatives. Does Form and the form components themselves serve your needs? Input shouldn’t be used directly, so please don’t rely on it!
Cheers,
Stephen