Orange-OpenSource / Orange-OpenSource/ouds-flutter
In `library`, add `accordion` component
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 5
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 9
Description
Description
As a user of the OUDS library
I want to be able to use the component
So that I can add this OUDS component in my own projects
As a user of the library
I want to be able to use the component
So that I have access to the documentation on how to use it
As a user of the Design System Toolbox app
I want to access the Component
So that I can understand how to use it:
- while using the demo app I can interact with the available options and observe the changes on the component itself
- I can see the code associated to the component customization
- I can copy and paste the code from the app based on the selected customization
- or when looking into the code of the app itself, I would also understand how to use it
Context
Verbatims from @MaximeTonnerre:
The "Accordion » components is ready on the design side.
The corresponding design tokens will be included in version 2.6 of the design token library.
Technically, the component is split into three separate versions:
- Accordion list item
- Accordion card item
- Accordion FAQ
Definition of Ready
- Have Figma specifications available
- Have tokens available
Definition of Done
To be defined
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Figma specifications and confirm how the available design tokens map to the three versions: accordion list item, card item, and FAQ. Then inspect the library and Design System Toolbox app entry points to determine the required component, documentation, demos, and copyable customization code. Definition of Done is still unspecified, so clarify acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, figma, flutter
- Domain
- design, documentation, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100