New components needed to build real-world apps (showcase gap analysis)

Offen
#1,346 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
bootstrap, csharp
Bereich
design, frontend

Rechercherichtung

Start by reviewing the 17 component gaps and their related issues, then compare them with the existing component conventions and the Showcase work in #1343. Refinement is needed to choose priorities and split this broad proposal into work items; done means those decisions are recorded and the selected components have actionable scopes.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

While building the 15 sample websites for the Showcase (#1343), we checked every screen against the components Blazor Bootstrap ships today. This issue lists the reusable components that are missing — building blocks that app developers need in their own projects, not showcase-only widgets. Each entry says what it is, which kinds of apps need it, and any existing issue it relates to.

Without these, the showcase (and real apps) fall back to hand-written Bootstrap HTML, which contradicts "built only with Blazor Bootstrap components".

Gap list

Phase 1 — layout and everyday building blocks (small, unblock most apps)
# Component What it does Needed by Related
1 Navbar Responsive top navigation: brand, links with active state, dropdowns, collapse on mobile, optional offcanvas mode, sticky/fixed placement, color schemes Marketing, E-commerce, Travel, Restaurant, Blog, LMS, Healthcare portals #1335, #742, #300, #1131
2 ButtonGroup / ToggleButtonGroup Grouped buttons and a segmented control with single- or multi-select binding (@bind-Value), sizes, vertical layout Filter pills, list/board view switch, monthly/annual billing, chart ranges (day/week/month) — every app new
3 InputGroup Prefix/suffix add-ons (icon, text, button) around any input component, including validation styling Search boxes, currency/units, "copy" buttons, password reveal — every app new
4 ListGroup (incl. selectable / checkbox list) Bootstrap list group with active item, badges, actions, flush style, single/multi selection Conversation lists, notification panels, settings menus, ticket queues on mobile, knowledge-base lists #1334, #1065
5 Timeline Vertical list of dated events with icon, color, and content template CRM activity, order tracking, ticket history, incident updates, audit logs #1306
6 Stepper / Wizard Numbered steps with per-step validation, next/back, optional linear mode, horizontal/vertical Checkout, appointment booking, money transfer, onboarding, sign-up #1336
7 Popover Rich-content popover (title + any markup), click/hover/focus triggers, placement Card previews on boards, calendar event peek, help hints, inline confirmations #1333, #725, #1048
Phase 2 — form inputs
# Component What it does Needed by Related
8 DateRangeInput Start/end date selection with presets (Last 7 days, This month…), min/max, validation Hotel stays, leave requests, analytics/finance/monitoring date filters new
9 RangeInput (dual handle) Min–max range slider binding a pair of values, with tick marks and formatted labels Price filters (shop, travel, food), budget ranges new (enhancement of RangeInput)
10 NumberInput spin buttons Optional −/+ buttons (quantity stepper) with min/max/step, keyboard and touch friendly Cart quantities, guests/rooms, seats new (enhancement of NumberInput)
11 TagInput Free-text chips with suggestions, paste splitting, max count, validation Ticket tags, blog tags, task labels, email recipients #1337
12 MultiSelect (searchable) Dropdown with search, checkboxes, select-all, chips, IEnumerable<T> binding, virtualization Category/amenity/assignee filters, user pickers #1338, #559, #1144
Phase 3 — larger composite components
# Component What it does Needed by Related
13 Chat Message list (user/assistant/system), avatars, timestamps, streaming text, typing indicator, composer with attachments AI assistant apps, support chat, team messaging branch feature/ai-chat-component
14 Calendar / Scheduler Month/week/day views with events, slot selection, event templates Appointment booking, leave calendar, course schedules, room booking #944
15 ImageGallery / Lightbox Thumbnail grid that opens a keyboard-navigable full-screen viewer with captions Product photos, property galleries, portfolios new
16 TreeView Hierarchical list with expand/collapse, selection, tri-state checks, lazy loading Knowledge-base categories, file explorers, org structures #1339
17 Scrollspy (optional) Highlights the current section in a table of contents while scrolling Long lessons, blog posts, docs pages #1159

Already covered (no new component needed)

Avatar/AvatarGroup, Badge, Breadcrumb, Card, Carousel, Collapse, ConfirmDialog, Dropdown, Grid, Modal, Offcanvas, Pagination, Placeholders, Progress, RatingInput, RichTextEditor, FileInput, SortableList (Kanban boards via shared Group), SplitView, Tabs, Toasts, Tooltip, Charts (BlazorExpress.ChartJS), GoogleMap, PdfViewer, Markdown, MindMap. KPI/stat tiles, pricing tables, heroes and empty states are compositions of Card/Badge/Icon and stay as markup patterns.

Expectations for every new component

  • Follows existing library conventions (component-specific Color/Size enums, localizable text parameters, Bootstrap-first CSS, disconnect-safe JS interop).
  • Supports .NET 8, 9 and 10; works in Blazor Server and WebAssembly.
  • Accessible (keyboard, ARIA, visible focus) in light and dark mode.
  • Demo page in both hosts, Docusaurus docs page, and home/navigation discovery entries.
  • Used by at least one Showcase site so it is proven in a real screen.

Open questions (for refinement)

  • Final priority and release grouping of the 17 items.
  • Which items become their own work items vs. stay in this one.
  • Whether ButtonGroup, InputGroup and spin buttons are new components or enhancements to existing ones.
  • Whether Chat continues from the feature/ai-chat-component branch.
Vorherrschende Sprache
HTML
Sterne
1.2k
Forks
111
Ø Merge
4 Min.
Gemergte PRs (30 T.)
55

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus vikramlearning/blazorbootstrap

Alle Issues in vikramlearning/blazorbootstrap

Ähnliche Issues

Weitere Issues zu Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.