Orange-OpenSource / Orange-OpenSource/ouds-android
In `library`, add `card` component
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 5
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 30
Description
Description
As a user of the library
I want to be able to use the component
So that I can add and configure 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
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
Design specifications
To be defined
Definition of Ready
- Have Figma specifications 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
No files, tests, entry points, Figma specifications, or concrete completion criteria are named. Start by obtaining the missing Figma specifications and defining the component's API, documentation, and demo-app behavior. Done should include an implemented, configurable card, documented usage, and demo code that can be inspected and copied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100