Zur Navigation Zum Inhalt Kontakt Menu Principles Foundation Accessibility Design System Guidelines Deutsch Français Italiano English Our design principles User-centred Recognisable Inclusive Reduced Holistic Self-explanatory Task-oriented Appropriate SBB Brand portal Logo Digital clock Rights of use Base colors Functional colors Off brand colors Icons Timetable icons Pictograms About accessibility Über diesen Guide Contact Further information Product Owner User Research Interaction Design Visual Design Development Content Design Testing What is a design system? Designing Coding FAQ Help Process Contribution Contact Overview Base Components Overview Base Components Overview Base Components Overview Releases Design Tokens Komponenten Overview Base Informationen Sense & Purpose Community Assets Instructions Power-Apps Digital banner ads SAP Design Guidelines App Icons Contribution

We invite you to actively participate in the further development and improvement of our design system. Your ideas, feedback and experience are of immense value in building a powerful, flexible and future-proof design system.
We greatly value your contribution and are confident that you will be key to further professionalizing our design system.

The most important Github links.

Manifestation Board Issues
Lean To the board Bug Report, Request for contributing, Feature request or enhancement, Question
Web (Legacy) To the board Bug Report, Request for contributing, Feature request or enhancement, Question
Lyne To the board Bug Report, Request for contributing, Feature request or enhancement, Question
Mobile iOS To the board Bug Report, Request for contributing, Feature request or enhancement, Question
Mobile Android/Flutter To the board Bug Report, Request for contributing, Feature request or enhancement, Question

Adding Content

There are several criteria that have to be met in order for a component or a design token to be incorporated into the design system. If your requirement meets the following criteria, it has a good chance of being included in the system:

Can be used on multiple occasions

Components that can be used on multiple occasions and are designed to be as generic as possible have a good chance of beeing accepted. We are happy to help with generalization, if necessary.

Contribute to the user experience principles

Components that contribute to our principles also have a good chance. Especially vital are the principles "recognisable", "inclusive", "self-explanatory" and "reduced".

Does not have a business logic

Components with business logic or attached services/APIs have no chance to be included. The business logic can change and is the responsibility of the business owners. Our teams are not organizationally able to run and monitor these changes/developments. However, in most cases the business logic can be extracted. We are happy to help with architectural issues.

Contribute to efficiency

Components that speed up the design and development process by reducing the need to perform repetitive or time-consuming tasks are good candidates for adoption into the design system.

Yes, no or yes & no.

Together we decide whether content should be included or not. This quiz is intended to help you decide whether a component belongs in the design system or should be developed in the project. In case of doubt/uncertainty: do not hesitate to contact us.

Imprint Contact Cookie settings