Description
Several recommendation cards generated by getRecommendations() point to routes that don't exist in the current Next.js app structure.
These recommendations are displayed through NextBestActionWidget.tsx, and when users click them, they are taken to non-existent pages that return 404 errors.
This creates a frustrating experience because the dashboard suggests useful next steps, but some of those actions cannot actually be accessed.
Why This Matters
The recommendation widget is designed to guide users toward relevant resources and activities. When a recommended action leads to a broken route, it interrupts the user journey and reduces trust in the platform.
Users may assume the feature is broken or that content has been removed when the issue is actually caused by incorrect route mappings.
Examples
In src/utils/recommendations.ts:
Non-existent /projects routes
href: '/projects?filter=web&level=beginner'
href: '/projects?filter=data-science&level=beginner'
No /projects route currently exists.
Non-existent open source issues route
href: '/open-source/issues?label=good-first-issue'
The application contains an /opensource route, but no /open-source/issues page.
Non-existent internship calendar route
href: '/internships/calendar'
The internship calendar is available through the resources page, not as a standalone route.
Non-existent pathways route
The application uses a different route structure, so /pathways results in a 404.
Non-existent community introduction route
href: '/community/introduce'
There is currently no /community/introduce page.
Impact
- Recommendation cards can lead users to 404 pages.
- Breaks the intended onboarding and discovery flow.
- Creates confusion for users following suggested next actions.
- Reduces the usefulness of the recommendation system.
Suggested Fix
Review all routes defined in src/utils/recommendations.ts and update them to match the actual pages available in src/app.
Potential corrections include:
- Replace invalid
/projects routes with the appropriate existing resource pages.
- Update
/open-source/issues to the correct open-source section.
- Redirect internship calendar recommendations to the resources page where the calendar is available.
- Replace
/pathways with the correct pathway route.
- Update
/community/introduce to an existing community page.
Acceptance Criteria
Description
Several recommendation cards generated by
getRecommendations()point to routes that don't exist in the current Next.js app structure.These recommendations are displayed through
NextBestActionWidget.tsx, and when users click them, they are taken to non-existent pages that return 404 errors.This creates a frustrating experience because the dashboard suggests useful next steps, but some of those actions cannot actually be accessed.
Why This Matters
The recommendation widget is designed to guide users toward relevant resources and activities. When a recommended action leads to a broken route, it interrupts the user journey and reduces trust in the platform.
Users may assume the feature is broken or that content has been removed when the issue is actually caused by incorrect route mappings.
Examples
In
src/utils/recommendations.ts:Non-existent
/projectsrouteshref: '/projects?filter=web&level=beginner'href: '/projects?filter=data-science&level=beginner'No
/projectsroute currently exists.Non-existent open source issues route
href: '/open-source/issues?label=good-first-issue'The application contains an
/opensourceroute, but no/open-source/issuespage.Non-existent internship calendar route
href: '/internships/calendar'The internship calendar is available through the resources page, not as a standalone route.
Non-existent pathways route
href: '/pathways'The application uses a different route structure, so
/pathwaysresults in a 404.Non-existent community introduction route
href: '/community/introduce'There is currently no
/community/introducepage.Impact
Suggested Fix
Review all routes defined in
src/utils/recommendations.tsand update them to match the actual pages available insrc/app.Potential corrections include:
/projectsroutes with the appropriate existing resource pages./open-source/issuesto the correct open-source section./pathwayswith the correct pathway route./community/introduceto an existing community page.Acceptance Criteria
src/utils/recommendations.ts.