Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

refactor: header used in "dashboard/*" should be a shared component

Open
#224 4 comments 0 reactions 0 assignees View on GitHub

@SirjanSingh is already working on this.

Since Dec 14, 2025.

  • #245 by @SirjanSingh — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

Start by locating the duplicated navbar code across dashboard, dashboard/messages, and dashboard/collaboration. Review the proposed components/Navbar.jsx location and compare the existing behavior, including tooltips and icons. Done means the affected views use one shared React component and the navbar remains consistent across them.

Written by the indexing model from the issue text.

Description

Current Behavior

The navbar code appears to be duplicated across multiple sections of the project.
dashboard, dashboard/messages, dashboard/collaboration, etc
This makes changes harder to maintain and increases the chance of inconsistencies (e.g., tooltip behavior, icon updates).

Proposed Improvement

Extract the navbar into a separate, reusable React component (e.g., components/Navbar.jsx) and import it wherever needed.

Why This Is Valuable

Reduces code duplication
Simplifies future updates
Prevents inconsistencies across pages
Improves project structure and maintainability

Additional Context

I will ensure the navbar behaves consistently across views.

@Saahi30 I'd like to work on this if its approved.

Dominant language
TypeScript
Stars
101
Forks
145
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/InPactAI

All issues in AOSSIE-Org/InPactAI

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.