Porsche Design SystemSearchNavigate to GitHub repository of Porsche Design SystemOpen sidebar
ConfiguratorExamplesUsageAccessibilityAPI
Tag Usage Use tags to label, categorize, or organize items using keywords that describe them. The following segment provides instructions for designers and developers regarding the appropriate utilization of this component in various situations. Do: Use to indicate or highlight a certain attribute of an item. Use to show that content is mapped to one or multiple categories. Use to indicate that a certain filter is active. Use short labeling for easy scanning. Have a large number of tags horizontally scrollable, swipeable, or navigable with arrows. Have tags in a predefined space and move to the next line once they meet the boundary. Use color themes such as success, neutral, warning, and error for better visual perception Include icons to improve the faster perception. Add a link for further explanation about the tag for better understandability (With modal). Add a link for additional information that is not necessary for the task completion (With modal). Don't: Don't use more than two words (only if necessary). Don't implement something else than a link or button. Don't use Tags for navigation.
Global settingsThemeChanges the theme of the application and any Porsche Design System component. It's possible to choose between forced theme light and dark. It's also possible to use auto, which applies light or dark theme depending on the operating system settings automatically.LightDarkAuto (sync with operating system)DirectionThe dir global attribute in HTML changes the direction of text and other content within an element. It's most often used on the <html> tag to set the entire page's direction, which is crucial for supporting languages that are written from right to left (RTL), such as Arabic and Hebrew. For example, using <html dir="rtl"> makes the entire page display from right to left, adjusting the layout and text flow accordingly.LTR (left-to-right)RTL (right-to-left)Text ZoomTo ensure accessibility and comply with WCAG 2.2 AA standards, it is mandatory for web content to support text resizing up to at least 200% without loss of content or functionality. Using relative units like rem is a best practice for achieving this, as they allow the text to scale uniformly based on the user's browser settings.100%130%150%200%