Wordmark exports in @atlaskit/logo are being deprecated

Hi folks :wave:

Bit of a general cleanup going on here at the moment. We’re currently looking at Wordmark in @atlaskit/logo.

For context, the @atlaskit/logo package currently has three exports per Atlassian Logo; a Wordmark, a LogoMark (in code this is the LogoIcon) and a Lockup - the latter is the composition of the first two elements. In practice, and in brand guidelines the presence of the Wordmark on its own is not meant to be possible but for historical reasons this export was supported to allow for the legacy navigation experience to grow / shrink the Lockup with constrained space.

This use case is no longer relevant and as such there is no reason to continue to support this component as an isolated export.

This affects many of the @atlaskit/logo exports in summary:

export {
   AtlassianIcon,
   AtlassianLogo,
-  AtlassianWordmark,
} from './atlassian-logo';
export { AtlassianStartLogo } from './atlassian-start-logo';
export {
   BitbucketIcon,
   BitbucketLogo,
-  BitbucketWordmark,
} from './bitbucket-logo';
export { CompassIcon, CompassLogo, CompassWordmark } from './compass-logo';
export {
   ConfluenceIcon,
   ConfluenceLogo,
-  ConfluenceWordmark,
} from './confluence-logo';
export type { LogoProps } from './types';
export { HalpIcon, HalpLogo, HalpWordmark } from './halp-logo';
export { HipchatIcon, HipchatLogo, HipchatWordmark } from './hipchat-logo';
export {
   JiraAlignIcon,
   JiraAlignLogo,
-  JiraAlignWordmark,
} from './jira-align-logo';
export { JiraCoreIcon, JiraCoreLogo, JiraCoreWordmark } from './jira-core-logo';
export { JiraIcon, JiraLogo, JiraWordmark } from './jira-logo';
export {
   JiraServiceDeskIcon,
   JiraServiceDeskLogo,
-  JiraServiceDeskWordmark,
} from './jira-service-desk-logo';
export {
   JiraServiceManagementIcon,
   JiraServiceManagementLogo,
-  JiraServiceManagementWordmark,
} from './jira-service-management-logo';
export {
   JiraSoftwareIcon,
   JiraSoftwareLogo,
-  JiraSoftwareWordmark,
} from './jira-software-logo';
export {
   JiraWorkManagementLogo,
-  JiraWorkManagementWordmark,
   JiraWorkManagementIcon,
} from './jira-work-management-logo';
export {
   OpsGenieIcon,
   OpsGenieLogo,
-  OpsGenieWordmark,
   OpsgenieIcon,
   OpsgenieLogo,
-  OpsgenieWordmark,
} from './opsgenie-logo';
export {
   StatuspageIcon,
   StatuspageLogo,
-  StatuspageWordmark,
} from './statuspage-logo';

If you are using any of these exports you’ll need to take action as they will no longer be supported.

1 Like

This may sound a bit snarky, but I’m glad to see the design system team has their priorities straight! The entire development community is in an existential crisis over which frontend libraries to use, which did not even draw a response, but yes, removing word marks was definitely also on the top of the list!

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.