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

Remove the landing page

Open Beginner friendly
  • Is something wrong?
#847 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
frontend

Research direction

Start with angular-client/src/pages/landing-page, then read angular-client/src/app/app-routing.module.ts and the nav bar files mentioned in the issue, including their use of CurrentRunDisplayComponent. Decide how the empty route should reach the placeholder or existing page, and preserve or remove the nav link and component import consistently. Done when the landing page is removed and root navigation reaches the chosen simple destination without a full redesign.

Written by the indexing model from the issue text.

Description

by: ai-assisted frontend good-for: new-member spike
What

Remove the angular-client landing page. Opening Argos (the root path) and clicking the home logo in the nav bar should take people straight to the graph page.

Requirements
  • Opening the root path lands on the graph page
  • The home logo in the nav bar goes to the graph page
  • Old /landing links and bookmarks still end up on the graph page
  • The landing page and anything only it used are deleted
  • The nav bar's current-run display still works
Notes
  • The nav bar imports CurrentRunDisplayComponent from the landing page's components folder; move it somewhere shared before deleting the page.
  • app-routing.module.ts redirects the empty path to the landing route, and app-routes.ts defines landingRoute; the nav bar's homeNavItem uses it.
  • The landing page renders many widgets (acceleration graphs, speed, torque, brake pressure, connection, viewers, and more) and has a mobile variant. Check which are used elsewhere before deleting them.
  • Open question: whether the graph page works well enough on mobile to be the landing spot there too.
Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
3d 12h
Merged PRs (30d)
33

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 Northeastern-Electric-Racing/Argos

All issues in Northeastern-Electric-Racing/Argos

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.