Control items pages should have both item and standalone versions in cards at the top
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- bootstrap, css
- Domain
- documentation
Research direction
Start by locating the documentation pages for radio buttons, checkboxes, switches, and the existing component-group cards, then compare how other groups organize their names and lists. Done means the three control-item groups use pluralized names and show both item and standalone versions prominently in cards at the top.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have searched for duplicate or closed feature requests
- I have read the contributing guidelines
Proposal
Control items (radio button, checkbox and switch) should be organized like other component groups : pluralized names (Checkboxes) and component lists in cards at the top.
Motivation and context
We need to display more prominently the standalone versions of the radio buttons, checkboxes and switches.
People miss them and do not understand what they should put in a table for example.
- Dominant language
- CSS
- Stars
- 219
- Forks
- 61
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 12
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.
More from Orange-OpenSource/Orange-Boosted-Bootstrap
-
📖 documentation 🧩 enhancement
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
🐞 bug 🧰 library
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
🛠️ technical github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Orange-OpenSource/Orange-Boosted-Bootstrap#3780 · 1 reaction ·
-
🐞 bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Orange-OpenSource/Orange-Boosted-Bootstrap#3775 · 1 comment ·
-
🐞 bug 👂 accessibility 📖 documentation asked by community
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Orange-OpenSource/Orange-Boosted-Bootstrap#3756 · 2 comments ·
All issues in Orange-OpenSource/Orange-Boosted-Bootstrap
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100