@porsche-design-system/components-react 4.5.0 → 4.6.0-rc.0

package/skill/references/components/p-checkbox/p-checkbox.md

@@ -0,0 +1,122 @@
+# p-checkbox
+
+The `p-checkbox` component wraps the native HTML input type `checkbox` form element. Checking one box doesn't uncheck other Checkboxes. By default, Checkboxes are not selected.
+
+> **Firefox Form Restore Bug**
+>
+> Firefox has a known bug where it incorrectly restores form state for form-associated custom elements with shadow DOM on page reload. Checkbox values may appear inside unrelated `input-text` fields in the same form under certain conditions. To work around this, add the native HTML attribute `autocomplete="off"` to all checkbox form elements. See [Firefox Bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1986953) for details.
+
+A `label` is a caption which informs the user what information a particular form field is asking for. The `p-checkbox` component can be used with or without a label, but it's recommended to keep the label visible for better accessibility whenever possible. When used without a label, it's best practice to provide a descriptive label text for screen readers.
+
+## Usage
+
+### Do:
+
+- Use for a list of options when you want the user to select one, none, or multiple options.
+- Use when an explicit action is required to apply to settings.
+- Use the default view for checkboxes when no option is selected.
+- Use the indeterminate state only as a visual state and not as a direct user interaction.
+- Nest when a parent and child relationship is needed.
+- Use short and descriptive label text for each checkbox option.
+- Provide validation messages for each checkbox option if needed.
+- Set vertically left-aligned for better scannability.
+
+### Don't:
+
+- Avoid using when you have more than 8 options to choose from or consider using a [Select](../p-select/p-select.md).
+- Don't mix [Radio Group](../p-radio-group/p-radio-group.md) options with checkboxes.
+- Don't change the selection of another checkbox when a nested one is clicked. The only exception is when a checkbox is used to make a bulk selection of multiple items.
+
+---
+
+## Related Components
+
+- [Radio Group](../p-radio-group/p-radio-group.md)
+- [Select](../p-select/p-select.md)
+
+## Accessibility support
+
+### Keyboard
+
+| Key / state | Function |
+| --- | --- |
+| `Tab`, `Shift-Tab` | Moves focus to the next (or previous) focusable element. |
+| `Space` | Activates/Deactivates checkbox. |
+
+### ARIA enhancements
+
+#### Internal **ARIA** that is managed by the component:
+
+| ARIA | Usage |
+| --- | --- |
+| `aria-describedby="IDREF"` | References the accessible description of status messages. |
+| `role="status"`, `role="alert"` | When `message` and `state` or `loading` prop change, the status message is announced. |
+| `aria-hidden="true"` | If `required` attribute is set, the visible asterisk indicator is hidden from assistive technologies. |
+| `aria-invalid="true"` | If `error` state is set. |
+
+## Development considerations
+
+### Disabled state
+
+In general, avoid using the `disabled` state. Disabled elements are no longer focusable and may be missed by screen reader users. They can also confuse sighted users if the reason they are disabled is not made clear.
+
+### Common do's and don'ts
+
+- **Do** provide a clear `label` that describes what the checkbox controls.
+- **Do** use the component state/message API so validation and status changes are announced.
+- **Do** use clear error wording that helps users recover.
+- **Don't** use `hide-label` without an accessible name.
+- **Don't** use `hide-label` when it is not clear what the checkbox controls.
+
+## API
+
+### Properties
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `checked` | `boolean` | `false` | Reflects the checkbox's current checked state and allows setting the initial checked value on load. |
+| `compact` | `boolean` | `false` | Reduces the checkbox size and spacing for a more compact layout. |
+| `disabled` | `boolean` | `false` | Disables the checkbox, preventing all interaction. The value is not submitted with the form. |
+| `form` | `string` | `undefined` | Associates the checkbox with a form element by its ID when not directly nested inside it. |
+| `hideLabel` | `boolean`<br>`BreakpointCustomizable<boolean>` | `false` | Hides the visible label while keeping it accessible to screen readers. Supports responsive breakpoint values. |
+| `indeterminate` | `boolean` | `false` | Puts the checkbox into an indeterminate state, indicating that a group of child items is only partially selected. |
+| `label` | `string` | `''` | Sets the visible label text displayed next to the checkbox. |
+| `loading` _(experimental)_ | `boolean` | `false` | @experimental Disables the checkbox and displays a loading spinner to indicate an ongoing operation. |
+| `message` | `string` | `''` | Sets the validation feedback message displayed below the checkbox when `state` is `success` or `error`. |
+| `name` | `string` | `''` | Sets the name submitted with the form data to identify this checkbox's value on the server. |
+| `required` | `boolean` | `false` | Marks the checkbox as required — form submission is blocked unless the checkbox is checked. |
+| `state` | `'none'` `'error'` `'success'` | `'none'` | Sets the validation state, controlling the visual appearance and style of the feedback message (`none`, `success`, `error`). |
+| `value` | `string` | `'on'` | Sets the value submitted with the form data when the checkbox is checked. Unchecked checkboxes are excluded from form submissions. |
+
+### Events
+
+| Event | Type | Description |
+| --- | --- | --- |
+| `blur` | `CustomEvent<CheckboxBlurEventDetail>`<br>`Event` | Emitted when the checkbox loses focus. |
+| `change` | `CustomEvent<CheckboxChangeEventDetail>`<br>`Event` | Emitted when the user changes the checked state of the checkbox. |
+
+### Slots
+
+| Slot | Required | Allowed tag names | Description |
+| --- | --- | --- | --- |
+| `label` | no | — | Shows a label. Only [phrasing content](https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Content_categories#Phrasing_content) is allowed. |
+| `label-after` | no | — | Places additional content after the label text (for content that should not be part of the label, e.g. external links or `p-popover`). |
+| `message` | no | — | Shows a state message. Only [phrasing content](https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Content_categories#Phrasing_content) is allowed. |
+
+### CSS Variables
+
+| CSS Variable | Default | Description |
+| --- | --- | --- |
+| `--p-checkbox-border-color` | — | 🧪Experimental: Border colors of Checkbox. Should be used to override the default border color in different states (e.g., hover, focus, error), e.g. when the Checkbox is wrapped inside a custom label. |
+| `--p-checkbox-background-color` | — | 🧪Experimental: Background color of Checkbox. |
+| `--p-checkbox-icon-color` | — | 🧪Experimental: Checkmark icon color of Checkbox. |
+
+## Examples
+
+| Example | When to use | File |
+| --- | --- | --- |
+| Default | Minimal default configuration. | [./examples/Default.tsx](./examples/Default.tsx) |
+| Form | The `p-checkbox` can be integrated into a form in two ways: **controlled** or **uncontrolled**, depending on your needs. | [./examples/Form.tsx](./examples/Form.tsx) |
+| Indeterminate | Mask the visual appearance of a checkbox which has a state in-between checked and unchecked. | [./examples/Indeterminate.tsx](./examples/Indeterminate.tsx) |
+| Slots | Use named slots when `label` or `message` need markup such as a link. | [./examples/Slots.tsx](./examples/Slots.tsx) |
+| Custom wrapped label (🧪Experimental) | The `p-checkbox` component also supports a custom wrapped `label` by wrapping the component in a `label` tag. | [./examples/WrappedLabel.tsx](./examples/WrappedLabel.tsx) |

package/skill/references/components/p-crest/examples/CustomClickableArea.tsx

@@ -0,0 +1,10 @@
+import React from 'react';
+import { PCrest } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PCrest href="https://porsche.com" className="p-static-md" aria={{'aria-label': 'Porsche Homepage'}}></PCrest>
+    </>
+  )
+}

package/skill/references/components/p-crest/examples/Default.tsx

@@ -0,0 +1,10 @@
+import React from 'react';
+import { PCrest } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PCrest></PCrest>
+    </>
+  )
+}

package/skill/references/components/p-crest/examples/Link.tsx

@@ -0,0 +1,10 @@
+import React from 'react';
+import { PCrest } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PCrest href="https://porsche.com" aria={{'aria-label': 'Porsche Homepage'}}></PCrest>
+    </>
+  )
+}

package/skill/references/components/p-crest/p-crest.md

@@ -0,0 +1,65 @@
+# p-crest
+
+The `p-crest` gives the Porsche brand a distinctive look, sets it apart from others within the overall external image and represents the quality of the product.
+
+> **Usage hint**
+>
+> This component shall only be used on viewports below 480px (breakpoint "S"). Otherwise, [p-wordmark](../p-wordmark/p-wordmark.md) has to be used.
+
+You can use native `click`, `focus`, `focusin`, `blur` and `focusout` events on the `p-crest`.
+
+## Usage
+
+### Do:
+
+- Use the [Wordmark](../p-wordmark/p-wordmark.md) as the main brand identifier.
+- Use the crest only as an additional small brand identifier (e.g., within contact cards).
+- Switch from the wordmark to the crest on small viewports below 480px (automatically implemented in global navigation and footer).
+
+### Don't:
+
+- Use the crest as the primary brand identifier by default.
+
+---
+
+## Related Components
+
+- [Wordmark](../p-wordmark/p-wordmark.md)
+
+## Accessibility support
+
+### ARIA enhancements
+
+#### External **ARIA** provided by the `aria` property:
+
+| ARIA | Usage |
+| --- | --- |
+| `aria-label` | Defines a string value that labels the interactive element. |
+| `aria-current` | Exposes the current state of the link. |
+| `aria-haspopup` | Defines that the link opens a popup (e.g. `dialog`). |
+
+## Development considerations
+
+### Common do's and don'ts
+
+- **Do** pass ARIA attributes through the `aria` prop when the crest is linked.
+- **Do** provide a descriptive `aria-label` for linked crests, for example "Porsche home".
+- **Don't** add native `aria-*` attributes directly on the component host.
+
+## API
+
+### Properties
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `aria` | `CrestAriaAttribute` | `undefined` | Sets ARIA attributes on the anchor element to improve accessibility when the crest is used as a link. |
+| `href` | `string` | `undefined` | When set, renders the crest as an anchor element navigating to this URL when clicked. |
+| `target` | `'_self'` `'_blank'` `'_parent'` `'_top'` `'string'` | `'_self'` | Specifies where to open the linked URL (e.g. `_self`, `_blank`). Only applies when `href` is set. |
+
+## Examples
+
+| Example | When to use | File |
+| --- | --- | --- |
+| Default | Minimal default configuration. | [./examples/Default.tsx](./examples/Default.tsx) |
+| Link | The Porsche Crest will be rendered as `<a>`-tag as soon as an `href` is provided. | [./examples/Link.tsx](./examples/Link.tsx) |
+| Custom clickable/focusable area | Sometimes it may be useful to enlarge the clickable/focusable area of the Porsche Crest. | [./examples/CustomClickableArea.tsx](./examples/CustomClickableArea.tsx) |

package/skill/references/components/p-display/examples/Color.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDisplay } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDisplay tag="h3" color="inherit" className="text-[deeppink]">
+        The quick brown fox jumps over the lazy dog
+      </PDisplay>
+    </>
+  )
+}

package/skill/references/components/p-display/examples/Default.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDisplay } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDisplay>
+        The quick brown fox jumps over the lazy dog
+      </PDisplay>
+    </>
+  )
+}

package/skill/references/components/p-display/examples/Semantics.tsx

@@ -0,0 +1,18 @@
+import React from 'react';
+import { PDisplay } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDisplay tag="h3">
+        The quick brown fox jumps over the lazy dog
+      </PDisplay>
+
+      <PDisplay>
+        <h3>
+          The quick brown fox jumps over the lazy dog
+        </h3>
+      </PDisplay>
+    </>
+  )
+}

package/skill/references/components/p-display/examples/Size.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDisplay } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDisplay tag="h3" size="inherit" className="text-[5rem]">
+        The quick brown fox jumps over the lazy dog
+      </PDisplay>
+    </>
+  )
+}

package/skill/references/components/p-display/examples/SizeResponsive.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDisplay } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDisplay tag="h3" size={{'base': 'medium', 'l': 'large'}}>
+        The quick brown fox jumps over the lazy dog
+      </PDisplay>
+    </>
+  )
+}

package/skill/references/components/p-display/p-display.md

@@ -0,0 +1,78 @@
+# p-display
+
+> **Deprecated:** since v4.0.0, will be removed with next major release. Please use `p-heading` instead.
+
+`p-display` is used to highlight and specify heading styling and hierarchy in documents.
+
+> **Recommendation**
+>
+> Although the component is very sophisticated, it's recommended (if possible) to use the corresponding utility classes of the "@porsche-design-system/components-{js | angular | react | vue}/tailwindcss" sub-package or any of the other styling solutions for best performance since way less DOM nodes are required to render. Further information can be found [here](../../styles/tailwindcss.md).
+
+## Usage
+
+p-display is used to highlight and specify heading styling and hierarchy.
+
+### Do's:
+
+- Use p-display for standout moments like hero intros, emotional statements, or key statistics.
+- Choose from display-small, display-medium, or display-large depending on the visual weight required.
+- Center-align p-display styles for marketing, landing, or intro sections to enhance visual impact.
+- Ensure generous spacing around p-display elements to give them room to breathe.
+
+### Don't:
+
+- Don’t use p-display styles for standard section headings or body text—use p-heading or p-text instead.
+- Don’t mix multiple p-display sizes on the same screen unless clearly structured (e.g. in a visual hierarchy).
+
+## Accessibility support
+
+This component does not include any special accessibility features.
+
+## Development considerations
+
+### Heading hierarchy
+
+While using the `Display` component, take care of the correct heading hierarchy which can be adjusted through the `tag` property. Keep in mind that the visual appearance must not always be identical with the semantic hierarchy.
+
+#### Best practices
+
+- Use one unique `h1` per page that describes what that page is about.
+- Use headings to describe the content below. Do not use an HTML heading just to make the text appear bigger or stand out.
+- Use heading levels like the index of a book: hierarchical.
+- Do not choose a heading by its size, but by its level in the context of the content.
+- Heading hierarchy should not increase by more than one level at a time.
+- Do not skip a heading level from the top down.
+
+### Common do's and don'ts
+
+- **Do** use the `tag` prop to reflect semantic hierarchy, not just visual `size`.
+- **Do** keep one unique `h1` per page for the primary page topic.
+- **Don't** use `tag="h1"` on display text that is not the main page title.
+
+## API
+
+### Properties
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `align` | `'start'` `'center'` `'end'` `'inherit'` | `'start'` | Sets the horizontal text alignment (`start`, `center`, `end`, or `inherit`). |
+| `color` | `'primary'` `'inherit'` | `'primary'` | Sets the text color using PDS color tokens. |
+| `ellipsis` | `boolean` | `false` | Truncates the text with an ellipsis when it overflows the container on a single line. |
+| `size` | `'small'` `'medium'` `'large'` `'inherit'`<br>`BreakpointCustomizable<DisplaySize>` | `'large'` | Sets the visual text size. Supports responsive breakpoint values. |
+| `tag` | `undefined` `'h1'` `'h2'` `'h3'` `'h4'` `'h5'` `'h6'` | `undefined` | Sets the HTML heading tag (h1–h6) for correct document outline placement. When omitted, the tag is inferred from `size`. |
+
+### Slots
+
+| Slot | Required | Allowed tag names | Description |
+| --- | --- | --- | --- |
+| _(default)_ | no | — | Default slot for the display text. |
+
+## Examples
+
+| Example | When to use | File |
+| --- | --- | --- |
+| Default | Minimal default configuration. | [./examples/Default.tsx](./examples/Default.tsx) |
+| Size | There are predefined fluid text sizes for the component which should cover most use cases. | [./examples/Size.tsx](./examples/Size.tsx) |
+| Responsive | Responsive | [./examples/SizeResponsive.tsx](./examples/SizeResponsive.tsx) |
+| Semantics | To provide more contextual HTML semantics you can either pass them with the `tag` property or directly inside a slot. | [./examples/Semantics.tsx](./examples/Semantics.tsx) |
+| Color | Predefined theme-based colors are available, but `inherit` can also be used to define a custom color. | [./examples/Color.tsx](./examples/Color.tsx) |

package/skill/references/components/p-divider/examples/Default.tsx

@@ -0,0 +1,10 @@
+import React from 'react';
+import { PDivider } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <PDivider></PDivider>
+    </>
+  )
+}

package/skill/references/components/p-divider/examples/Responsive.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDivider } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <div className="lg:flex lg:h-[150px]">
+        <PDivider direction={{'base': 'horizontal', 'l': 'vertical'}}></PDivider>
+      </div>
+    </>
+  )
+}

package/skill/references/components/p-divider/examples/Vertical.tsx

@@ -0,0 +1,12 @@
+import React from 'react';
+import { PDivider } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  return (
+    <>
+      <div className="flex h-[100px]">
+        <PDivider direction="vertical"></PDivider>
+      </div>
+    </>
+  )
+}

package/skill/references/components/p-divider/p-divider.md

@@ -0,0 +1,49 @@
+# p-divider
+
+The `p-divider` is used as 'horizontal or vertical rule' and displays a dividing line. The component is self-closing. Slotted content between the component tags won't be displayed.
+
+## Usage
+
+### Do:
+
+- Use to create a visual separation between related sections of content.
+- Use to separate content into clear groups.
+- Use when other options for structuring content are not sufficient.
+
+### Don't:
+
+- Don't use dividers to structure content, rather work with more space for clustering
+- Don't use it for decorative purposes unless it's necessary.
+- Avoid full-bleed dividers to separate page sections.
+
+## Accessibility support
+
+This component does not include any special accessibility features.
+
+## Development considerations
+
+### Structure
+
+A divider is visual separation only. Use headings, landmarks, or section structure to communicate content groups.
+
+### Common do's and don'ts
+
+- **Do** pair dividers with headings or landmarks that describe the sections they separate.
+- **Don't** rely on a divider alone to communicate a new major section.
+
+## API
+
+### Properties
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `color` | `'contrast-lower'` `'contrast-low'` `'contrast-medium'` `'contrast-high'` | `'contrast-lower'` | Sets the color of the divider line using PDS contrast tokens. |
+| `direction` | `'vertical'` `'horizontal'`<br>`BreakpointCustomizable<DividerDirection>` | `'horizontal'` | Sets the orientation of the divider to `horizontal` or `vertical`. Supports responsive breakpoint values. |
+
+## Examples
+
+| Example | When to use | File |
+| --- | --- | --- |
+| Default | Minimal default configuration. | [./examples/Default.tsx](./examples/Default.tsx) |
+| Vertical | **Hint:** The component has not an implicit vertical height unless we set a container which provides it or define the height on the component itself. | [./examples/Vertical.tsx](./examples/Vertical.tsx) |
+| Responsive | You can change the divider's direction by using different major breakpoints `xs`, `s`, `m`, `l`, `xl`. | [./examples/Responsive.tsx](./examples/Responsive.tsx) |

package/skill/references/components/p-drilldown/examples/CustomContent.tsx

@@ -0,0 +1,164 @@
+import React from 'react';
+import { useState } from 'react';
+import { PButton, PButtonTile, PDrilldown, PDrilldownItem, PDrilldownLink, PLink, PModelSignature, type DrilldownUpdateEventDetail } from '@porsche-design-system/components-react';
+
+export const Example = () => {
+  const [activeIdentifier, setActiveIdentifier] = useState("id-1");
+  const [open, setOpen] = useState(false);
+
+  const onClick = () => {
+    setOpen(true);
+  }
+  const onUpdate = (e: CustomEvent<DrilldownUpdateEventDetail>) => {
+    setActiveIdentifier(e.detail.activeIdentifier);
+  }
+  const onDismiss = () => {
+    setOpen(false);
+  }
+
+  return (
+    <>
+      <nav aria-label="Main">
+        <PButton type="button" aria={{'aria-haspopup': 'dialog'}} onClick={onClick}>
+          Open Drilldown
+        </PButton>
+        <PDrilldown open={open} activeIdentifier={activeIdentifier} className="[--p-drilldown-grid-template:repeat(5,auto)_minmax(0,1fr)/auto]" onUpdate={onUpdate} onDismiss={onDismiss}>
+          <PDrilldownItem identifier="id-1" label="Motorsport" className="[--p-drilldown-grid-template:auto/repeat(2,minmax(0,1fr))] [--p-drilldown-gap:0px_16px]">
+            <PDrilldownItem identifier="id-1-1" label="718">
+              <PModelSignature slot="header" model="718"></PModelSignature>
+              <PButtonTile slot="button" label="Some label" description="718" weight="semi-bold" compact={true} aspectRatio={{'base': '1/1', 's': '9/16'}} className="mb-fluid-sm">
+                <img srcSet="assets/porsche-963@2x.webp 2x" src="assets/porsche-963.webp" width={636} height={847} alt="Porsche 963" />
+              </PButtonTile>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+            </PDrilldownItem>
+            <PDrilldownItem identifier="id-1-2" label="911">
+              <PModelSignature slot="header" model="911"></PModelSignature>
+              <PButtonTile slot="button" label="Some label" description="911" weight="semi-bold" compact={true} aspectRatio={{'base': '1/1', 's': '9/16'}} className="mb-fluid-sm">
+                <img srcSet="assets/porsche-963@2x.webp 2x" src="assets/porsche-963.webp" width={636} height={847} alt="Porsche 963" />
+              </PButtonTile>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+            </PDrilldownItem>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#" aria-current="page">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+          </PDrilldownItem>
+          <PDrilldownItem identifier="id-2" label="Some label">
+            <PDrilldownItem identifier="id-2-1" label="Some label">
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+            </PDrilldownItem>
+            <PDrilldownItem identifier="id-2-2" label="Some label">
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+              <PDrilldownLink href="#">
+                Some anchor
+              </PDrilldownLink>
+            </PDrilldownItem>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+          </PDrilldownItem>
+          <PDrilldownItem identifier="id-3" label="Some label">
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+          </PDrilldownItem>
+          <PDrilldownItem identifier="id-4" label="Some label">
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+          </PDrilldownItem>
+          <PDrilldownItem identifier="id-5" label="Some label">
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+            <PDrilldownLink href="#">
+              Some anchor
+            </PDrilldownLink>
+          </PDrilldownItem>
+          <PLink href="#" variant="secondary" icon="external" className="self-end">
+            Some external anchor
+          </PLink>
+        </PDrilldown>
+      </nav>
+    </>
+  )
+}