Remove Card from Open-UI Scope
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Cards are broad components that are used for various means and describe a "View" in most cases. These take an arbitrary number of inputs, have very different interface visualizations, and are too broad to categorize as a core component. Each design system uses Cards differently depending on its product area.
Essentially, anything can be categorized as a "card", from a User Profile to an Article Preview to a Results view. I believe this group is focused on core HTML elements (such as form elements) and improving them on the web platform as generics. In that spirit, we should remove Card from the Open-UI scope.
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 Card research page and the repository’s Open-UI scope materials to identify how Card is represented and referenced. Confirm the project’s scope decision, remove Card from the relevant scope content, and check that no remaining references present it as an in-scope core component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100