### Description We gathered insights from the community about a new component that matches our planned tree list component. - [ ] Do a research of the miller columns (https://en.wikipedia.org/wiki/Miller_columns) and - [ ] Create concept in Onyx Style (possible feature: Default, States, Levels, Folder) ### Example <img width="1007" height="263" alt="Image" src="https://github.com/user-attachments/assets/f2752e12-0e22-4226-92ed-8bc9474d5f0b" /> <img width="954" height="606" alt="Image" src="https://github.com/user-attachments/assets/d2326832-1adc-4db3-a17e-637ef5f8bae0" /> ### DEV handover checklist DEV handover done with: @ADD_DEV_NAME_HERE **Component** - [ ] defined main component name - [ ] defined which support components are used and how they are named - [ ] component has been hidden from publishing (until its implemented) - the following is explained to the DEV and documented: - [ ] all properties - [ ] truncation - [ ] responsiveness / wrapping behavior - [ ] min / max width **Documentation** - [ ] category for Figma and Storybook is defined - [ ] examples that should be shown in Storybook are defined and documented in Figma (documentation file) - [ ] component status "planned" has been added to the [docs overview](https://onyx.schwarz/#components) **Other** - [ ] DEV has either refined an implementation ticket or at least created a blank issue with a title - [ ] follow-up UX tickets were created if necessary (add links below) - [ ] expand (figma) documentation with new results/decisions - [ ] make sure the results are transferred into the corresponding implementation or concept ticket
Description
We gathered insights from the community about a new component that matches our planned tree list component.
Example
DEV handover checklist
DEV handover done with: @ADD_DEV_NAME_HERE
Component
Documentation
Other