Migrate Schwarz icon consumers to new icon library

[larsrickert]

@JoCa96 Split up between UX and DEV

Depends on

• 1802

Why?

We want to have one unified icon library at Schwarz IT which is used by all UX designers (Figma) and developers. Technically we already synched @sit-onyx/icons with the Single-Source-of-Truth Figma file linked below (see #939).

We now want to onboard/migrate all consumers of the current SIT icon library to use the new unified library, this includes:

• STACKIT
• ODJ
• Twogo
• CoreUI

For responsible contacts for the consumers above, you can refer to @larsrickert

So eventually, all designers will consume the Icon Library - UX Schwarz IT Figma library and all developers will consume the @sit-onyx/icons npm package.

Design

Icon Library - UX Schwarz IT

Acceptance criteria

• onyx is migrated to use the new icon library
  • [ ] UX
  • [x] DEV
• STACKIT is migrated to use the new icon library
  • [ ] UX
  • [ ] DEV
• ODJ is migrated to use the new icon library
  • [ ] UX
  • [ ] DEV
• Twogo is migrated to use the new icon library
  • [ ] UX
  • [ ] DEV
• CoreUI is migrated to use the new icon library
  • [ ] UX
  • [ ] DEV
  • [ ] Icon repository is locked or deleted
  • [ ] npm package @scu/icons package is either deprecated or updated to use the latest @sit-onyx/icons
  • CoreUI's icon showcase is deleted and linked to the onyx icon docs instead
• [ ] @schwarz-ux/icons repo is locked/deleted and npm package is either deprecated or updated to use the latest @sit-onyx/icons
• [ ] all consumers are informed about the changes (e.g. via Teams)

Definition of Done

• [ ] follow-up tickets were created if necessary
• [ ] updated version + documentation is deployed
• [ ] Namings are aligned with Figma

Approval

• Deployed Docs
• [ ] approved by onyx designer @jannick-ux
• [ ] approved by onyx dev
• [ ] approved by STACKIT
• [ ] approved by ODJ
• [ ] approved by Twogo
• [ ] approved by CoreUI

[mj-hof]

Maybe a new or another nom package with a generic naming? @schwarzit/icons?

[mj-hof]

Check if we can display or link to an own url something like icons.schwarz (public) - is also a internal domain possible?

[larsrickert]

Maybe a new or another nom package with a generic naming? @schwarzit/icons?

The scope @schwarzit/* in npm was created by a former colleague at SIT, I am already in contact with @patrick246 to get access to it :) Imo @schwarzit/icons would be very nice!

[larsrickert]

Check if we can display or link to an own url something like icons.schwarz (public) - is also a internal domain possible?

@mj-hof I guess icons.schwarz should not be a problem, should I order it? Since its a public domain it may take some time before its ready for us. I would not make it internal since we also need it for onyx which is Open Source. Also internal domains are no longer allowed to use *.schwarz