Component code source and npm package links broken in new Atlassian Design docs

Atlassian Ecosystem Design
, , , , ,
1

For example: https://atlassian.design/components/button/code

If you go to the “Code” tab of a component in the Atlassian Design docs:

Naturally, you’ll open your search engine of choice and try to find the source code. Depending on which forum post or search engine result you happened to land on, you could end up in any of the following repos:

Various official and unofficial forum posts will lead you any one of these repos. Some examples:

TL;DR - If you fix up the links in the docs we won’t have to go down these rabbit holes.

2 Likes
2

I made a ticket for this as well: Log in with Atlassian account

3

@stephenmok @DanielDelCore I think this one is for you!

1 Like
4

Thanks for bringing this up, @HayleyTom! I can see the issue.

You’re right that atlassian-frontend-mirror is the correct public repository to go to, as it is the public mirror of our internal atlassian-frontend. I can confirm that officially. :slight_smile:

In other words, the contents of these are identical (note slightly different paths):

  • https://bitbucket.org/atlassian/atlassian-frontend/src/master/packages/design-system/* (internal Atlassian)
  • https://bitbucket.org/atlassian/atlassian-frontend-mirror/src/master/design-system/* (public mirror)

It’s on our backlog to improve those direct links on the docs. The above info should let you workaround that and get to the source whenever you need it. Apologies for the inconvenience in the meantime.

Cheers,
Stephen

1 Like
5

Hey folks - an update on the Source links on atlassian.design.

This morning a fix to the issue was merged and deployed to the production atlassian.design site. Public components on that site should now correctly link to the public mirror from the Code tab on that website.

1 Like