Shared UI component set
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css, html, rust, typescript
- Domain
- accessibility, design, frontend
Research direction
This is an umbrella for 21 sub-issues, so pick one rather than the parent — Spinner (#777) comes first and is already in progress per the ordering. Read AGENTS.md Conventions → Accessibility and §4.5, then DEVELOPMENT.md §13.7.5 for the per-component checklist; components live in crates/web/src/components.rs and the shared tones/sizes in variants.rs. Done means the component, its gallery entry, the features/ui/components.feature axe-core and keyboard rows, and token pairs in scripts/check-contrast.ts all land in one pull request.
Written by the indexing model from the issue text.
Description
The maintainer's plan: a shared component for each widget the web UI needs, built in crates/web/src/components.rs, so pages stop building widgets of their own (AGENTS.md, Conventions → Accessibility; §4.5).
The bar for every component (#772): WCAG 2.2 AA in full when it merges, an accessibility contract row in §4.5, and every step of development.md §13.7.5: the component, its gallery entry with every state, axe-core and ARIA snapshot rows in features/ui/components.feature, and keyboard-only contract scenarios. Colors only from the tokens, each new pair in scripts/check-contrast.ts; sizes from the reader's text; logical properties; 320 px with 200 % text, right to left, dark and forced colors.
One vocabulary (#798): every component takes the shared tones (Primary, Secondary, Success, Warning, Error, Inherit), sizes (Small, Medium, Large, XLarge) and placements (Inline, Start, Center, End) from variants.rs, saying in its §4.5 contract which tones it supports where one makes no sense.
One pull request per sub-issue, off main, each landing on its own. A component that only the gallery uses is fine; moving the pages onto it is its own pull request when it changes every page (as the button migration does).
DESIGN.md is a guide and changes as the set grows: its native-control rules give way to the shared components (Button first), recorded in the same pull request that changes them.
Order: the sub-issues' "blocked by" links give it. Spinner first (in progress), then Icon, then Button; the rest follow their dependencies. #775 (WebKit's false contrast reading of native buttons) closes with the button migration.
- #777 Spinner
- #778 Icon (Lucide)
- #779 Button
- #780 Move every native button onto Button
- #781 Link
- #782 Input and text field
- #783 Button group
- #784 Popover
- #785 Tooltip
- #786 Dropdown menu
- #787 Alert
- #788 Banner
- #789 Toast on the shared look
- #790 Badge
- #791 Indicator
- #792 Tabs
- #793 Skeleton
- #794 Progress on the shared look
- #795 Pagination
- #796 Responsive navigation bar
- #797 Date and time picker
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 56m
- Merged PRs (30d)
- 349
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 nledford/Ladderback
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nledford/Ladderback#809 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nledford/Ladderback#759 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nledford/Ladderback#746 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#745 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#647 ·
Maintainers usually reply within 1 day
All issues in nledford/Ladderback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·