Skip to content

feat(typography): adopt system typography tokens - #2545

Draft
timowolf wants to merge 2 commits into
mainfrom
feat/apply-typography
Draft

feat(typography): adopt system typography tokens#2545
timowolf wants to merge 2 commits into
mainfrom
feat/apply-typography

Conversation

@timowolf

@timowolf timowolf commented Aug 12, 2026

Copy link
Copy Markdown
Member

Copy the typography map in element-theme and apply its tokens across theme and form styles.

Replace legacy input font variables with a single configurable input token while retaining
legacy scales that have no token equivalent.


Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@timowolf
timowolf requested review from a team as code owners August 12, 2026 13:43
@timowolf
timowolf marked this pull request as draft August 12, 2026 13:43
@timowolf
timowolf requested a review from spike-rabbit August 12, 2026 13:44
@spike-rabbit
spike-rabbit force-pushed the feat/apply-typography branch from bd13883 to f9b9224 Compare August 12, 2026 15:17
@spike-rabbit spike-rabbit changed the title feat: apply typography feat(typography): adopt system typography tokens Aug 12, 2026
Comment on lines +325 to +335
font-family: (
'SiemensSans Pro VF',
'SiemensSans Pro',
helvetica,
arial,
sans-serif
),
font-weight: 600,
font-size: 0.75rem,
line-height: 1,
letter-spacing: 0

@dr-itz dr-itz Aug 12, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry, but that is a big NO for me. this will apply all these unnecessary attributes each and every time. i.e. font-family and letter-spacing remain unchanged. this causes the resulting CSS to be bigger than needed. Can't we somehow set the defaults somewhere and only include these attributes if they deviate from the default?

also, I don't like the name si-typography-map. that's cumbersome to type and also misleading when all the consumer usually wants is the mixin. why not just 'typography'`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, fully agree. I just did not got to it yet. So far this is the file coming from design-tokens without any modifications.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

another point is to make the font-sizes into css vars for the density topic. We're still exploring, so it's unclear at this point. I anyway implemented this in the PoC in #2471

direct link for customization: https://d33c9dcnqinn2a.cloudfront.net/pr-2471/pages/element-examples/#/overview/si-theme/spacer-controls

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I put a more smarter mixin in the typography file. That only includes family and letter spacing if diverging from body.
I kept the filename to have in sync with the sdl repo. Please have a look and let me know what you think

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the density thing, this obviously does not work with the current sdl output. If needed I think we should then introduce it there.

@spike-rabbit
spike-rabbit force-pushed the feat/apply-typography branch 6 times, most recently from f93b287 to d1f88c5 Compare August 17, 2026 12:31
Copy the typography map in element-theme and apply its tokens across theme and form styles.

Replace legacy input font variables with a single configurable input token while retaining
legacy scales that have no token equivalent.
@spike-rabbit
spike-rabbit force-pushed the feat/apply-typography branch from d1f88c5 to b9bd70a Compare August 17, 2026 12:41
Use utility classes for host visibility, positioning, overflow, and stacking so the directives do not inject inline styles that violate strict CSP policies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants