ashutosh1919 / ashutosh1919/masterPortfolio
Hardcoded Navigation and Routing Improvements
- Dominant language
- JavaScript
- Stars
- 4.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
### Summary :
The `Header.js` component uses hardcoded navigation links and the `Main.js` container uses an older version of `react-router-dom` (Switch). Modernizing the routing and making the header data-driven would improve maintainability.
**File Path :** `components/header/Header.js` and `containers/Main.js`
**Code Improvement :**
```
// Suggested change in Header.js to use a configuration file
import { greeting } from "../../portfolio.js"; // Assume data is centralized
// Instead of hardcoded
{navigation_links.map((link) => (
{link.name}
))}
```
Contributor guide
Research direction
Start by reading components/header/Header.js and containers/Main.js to compare the current hardcoded links and routing usage with the issue's proposed direction. Check the project's installed routing version and existing portfolio configuration before deciding how navigation data should be represented. Done means navigation is configuration-driven, routing uses the modern API, and the portfolio still builds and navigates correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100