Porsche Design SystemSearchNavigate to GitHub repository of Porsche Design SystemOpen sidebar
IntroductionVanilla JSAngularReactVueNext JSRemix
Initialization Table of Contents The Porsche Design System is based on Web Components using Shadow DOM primarily for the following reasons: to encapsulate markup and styles to prevent overriding styles or attributes to use the same components with plain html and any JavaScript framework, without having to maintain multiple libraries and keeping them in sync Introduction While the NPM packages @porsche-design-system/components-{js|angular|react|vue} are primarily used for bootstrapping, typing support and framework typical developer experience, the web components themselves and all their assets are served from a CDN (cdn.ui.porsche.com and cdn.ui.porsche.cn). More information about this can be found under Performance. Architecture Porsche Design System Architecture To understand what is happening when a component's html tag is rendered in the browser and what can be done to improve the bootstrapping process, please read through the following pages carefully. No matter if or which framework you use, please continue with Vanilla Js since its behavior is the foundation for all others.
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%