Create migration guide for drawer #79
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for industrial-experience ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
flxlst09
reviewed
Aug 27, 2025
flxlst09
reviewed
Aug 27, 2025
flxlst09
requested changes
Aug 27, 2025
- moved drawer markdowns to legacy - fixed links - added migration guide to sidebar - fixed wrong quotation marks - fixed grammar mistakes
flxlst09
previously approved these changes
Aug 29, 2025
kathrinschalber
commented
Sep 9, 2025
tokyojen
requested changes
Sep 10, 2025
There was a problem hiding this comment.
still think this could be "Enhanced elevation"
|
|
||
|  | ||
|
|
||
| The next chapter of the Industrial Experience Design System is here. With this release we take a significant stept toward a shared design language across the organization. This version brings together thoughtful feature enhancements and essential style refinements, offering greater flexibility while reinforcing design consistency. |
There was a problem hiding this comment.
Suggested change
| The next chapter of the Industrial Experience Design System is here. With this release we take a significant stept toward a shared design language across the organization. This version brings together thoughtful feature enhancements and essential style refinements, offering greater flexibility while reinforcing design consistency. | |
| The next chapter of the Industrial Experience Design System is here. This version brings together thoughtful feature enhancements and essential style refinements, offering greater flexibility while reinforcing design consistency. |
|
|
||
|  | ||
|
|
||
| The time of confusing button variants is officially behind us. With this release, we’ve introduced a clear and intuitive naming convention: primary, secondary, and tertiary [buttons](/docs/components/button/guide). Now labeled exactly as such. This change improves clarity, making it easier to choose the right button for the right context. |
There was a problem hiding this comment.
Suggested change
| The time of confusing button variants is officially behind us. With this release, we’ve introduced a clear and intuitive naming convention: primary, secondary, and tertiary [buttons](/docs/components/button/guide). Now labeled exactly as such. This change improves clarity, making it easier to choose the right button for the right context. | |
| The time of confusing button naming is officially behind us. With this release, we’ve introduced a clear and intuitive naming convention: primary, secondary, and tertiary [buttons](/docs/components/button/guide). Now labeled exactly as such. This change improves clarity, making it easier to choose the right button for the right context. |
| sidebar_title: Upgrade to v4 | ||
| title: Upgrade to v4 | ||
| doc-type: banner | ||
| description: Welcome to the migration guide for upgrading from Siemens Industrial Experience design system v3 to v4. This guide introduces all major changes. |
There was a problem hiding this comment.
Suggested change
| description: Welcome to the migration guide for upgrading from Siemens Industrial Experience design system v3 to v4. This guide introduces all major changes. | |
| description: Welcome to the migration guide for upgrading from Siemens Industrial Experience design system V3 to V4. This guide support you through all the major changes. |
|
|
||
| ## TL;DR | ||
|
|
||
| - We upgrade to [Angular 20](#angular-20). |
There was a problem hiding this comment.
Suggested change
| - We upgrade to [Angular 20](#angular-20). | |
| - We upgraded to [Angular 20](#angular-20). |
| | `danger` | `false` | `true` | `danger-tertiary` | | ||
| </div> | ||
|
|
||
| For buttons without explicitly set variant, the default is used. As defaults differ between the button components, the renaming should happen component-specific. |
There was a problem hiding this comment.
Suggested change
| For buttons without explicitly set variant, the default is used. As defaults differ between the button components, the renaming should happen component-specific. | |
| For buttons without an explicit set variant, the default is used. As defaults differ between the button components, the renaming should be component-specific. |
There was a problem hiding this comment.
let me know if i misunderstood this section
| | `default` | `false` | `true` | `tertiary` | | ||
| </div> | ||
|
|
||
| #### Toggle button and Icon toggle button with default variant |
There was a problem hiding this comment.
Suggested change
| #### Toggle button and Icon toggle button with default variant | |
| #### Toggle button and icon toggle button with default variant |
| | `default` | `false` | `true` | `subtle-tertiary` | | ||
| </div> | ||
|
|
||
| Visually review your changes. Ensure that `subtle` variants are not mixed with the default button. |
There was a problem hiding this comment.
Suggested change
| Visually review your changes. Ensure that `subtle` variants are not mixed with the default button. | |
| We recommend you visually review your changes. Ensure that `subtle` variants are not mixed with the default button. |
|
|
||
| - Publishing a new 'AG Grid theme' library | ||
| - Deprecating AG Grid components from 'iX components' Figma library | ||
| - Manual replacement effort needed, there is no automated replacement possible |
There was a problem hiding this comment.
Suggested change
| - Manual replacement effort needed, there is no automated replacement possible | |
| - Note: Manual replacement effort needed, there is no automated replacement possible |
|
|
||
| ### Legacy theme | ||
|
|
||
| The previous elevation principle (v3.x) is reflected in the legacy themes and will be available for a smooth transition phase. |
There was a problem hiding this comment.
Suggested change
| The previous elevation principle (v3.x) is reflected in the legacy themes and will be available for a smooth transition phase. | |
| The previous elevation principle (V3.x) is reflected in the legacy themes and will be available for a smooth transition phase. |
There was a problem hiding this comment.
is there a timeline on this?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira issue: IX-3140