Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Component: more NavBar variants (centered, floating, mega menu, sidebar, minimal, search)

Abierto
  • ¿Algo no está bien?
#47 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, tailwindcss, typescript
Área
frontend, internationalization

Línea de trabajo

Start by reading the existing NavBar component and its shared locale data, then review issues #44–#46 for the keyboard, RTL, and preview requirements. The issue asks for one separately claimed variant per PR; choose a variant and identify its registry, barrel export, docs, demo, and test entry points. Done when that variant meets the listed requirements and its acceptance checks pass.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

component enhancement help wanted

Summary

NavBar is the only navigation component. Add more navbar variants so users can pick a layout without restyling the base one. Each variant is a separate component and a separate PR; comment below to claim one.

Proposed variants

Component Description
NavBarCentered Logo centered, links split left/right, language selector and CTA at the end.
NavBarFloating Detached, rounded "pill" bar that floats over content with a blurred backdrop, and shrinks on scroll.
NavBarMega Links can open a mega-menu panel with grouped sub-links and descriptions.
NavBarSidebar Vertical side navigation for docs and dashboards, collapsible to icons, with the language selector in the footer.
NavBarMinimal Logo plus language selector only, using LanguageSwitcherPill as the inline locale control.
NavBarWithSearch Base bar plus a search field / command-palette trigger (⌘K).

Requirements (every variant)

  • Same conventions as NavBar:
    • value / defaultValue / onValueChange for the locale.
    • locales: Locale[] from ./types.
    • linkComponent for router links.
    • Ref forwarding and passthrough of extra props to the root element.
  • Locale labels and flags from the shared ./locale-data module. No local copies.
  • Language menus use useListboxNavigation (#44) for keyboard support.
  • RTL: dir derived from the active locale, logical utilities only (start/end, ms/me, text-start). See #45.
  • Responsive with a mobile menu at narrow widths; dark mode.
  • Registry entry with correct registryDependencies (npm run test:registry must pass), a barrel export, a docs page with Installation / Usage / Props / Examples, a live demo, and tests.
  • Docs preview tall enough for the variant's popups (see #46).

Acceptance per PR

  • One variant per PR, linked to this issue.
  • lint, format:check, typecheck, test, build:lib, test:pack pass.
  • Screenshots: LTR and RTL, desktop and ~390px, light and dark.
Lenguaje dominante
TypeScript
Estrellas
39
Forks
16
Merge medio
2 d 12 h
PR fusionados (30 d)
10

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de babelize/babelize-elements

Todos los issues de babelize/babelize-elements

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.