Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No link to go back to homepage #54867

Closed
JLH13 opened this issue May 19, 2024 · 2 comments
Closed

No link to go back to homepage #54867

JLH13 opened this issue May 19, 2024 · 2 comments
Labels
platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. status: waiting triage This issue needs help from moderators and users to reproduce and confirm its validity and fix. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.

Comments

@JLH13
Copy link

JLH13 commented May 19, 2024

Describe the Issue

After I was on freeCodeCamp for a while, there was something I wanted to check on the homepage, which is: https://www.freecodecamp.org, and I noticed that there was no way to get back to that page. The “freeCodeCamp” graphic link at the top takes you to https://www.freecodecamp.org/learn. There are also no links at the upper right menu or on the bottom of the web page that will take you to https://www.freecodecamp.org. What I had to do was hit the back arrow many times until it took me back to https://www.freecodecamp.org. I would suggest that the “freeCodeCamp” graphic link at the top of the page take you to https://www.freecodecamp.org and not https://www.freecodecamp.org/learn, since there is already a link to that in the upper right menu.

Affected Page

https://www.freecodecamp.org

Steps to Reproduce

  1. Go to https://www.freecodecamp.org
  2. Click on any of the links that take you to a different page.
  3. Try to get back to https://www.freecodecamp.org without using the back arrow.

Expected behavior

There should be a link that takes the user back to https://www.freecodecamp.org when they are not on that page.

Screenshots

No response

System

  • Device: 2020 Apple MacBook Air M1
  • OS: Sonoma 14.0
  • Browser: Safari
  • Version: 17.0

Additional context

No response

@JLH13 JLH13 added status: waiting triage This issue needs help from moderators and users to reproduce and confirm its validity and fix. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc. labels May 19, 2024
@gikf gikf added the platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. label May 20, 2024
@VP-66
Copy link
Contributor

VP-66 commented May 20, 2024

Hi there! I have also experienced this same situation and thought of the same improvement - it makes logical sense for the title graphic to re-direct to "https://www.freecodecamp.org/" as compared to "https://www.freecodecamp.org/learn".

If the owners are happy with change, I can help to work on it :)

@sbsangu sbsangu mentioned this issue May 20, 2024
4 tasks
@raisedadead
Copy link
Member

Thank you for reporting this, but this behavior is a conscious design choice. Our analytics tell us that people prefer using the learn map more than the landing page – which is optimized for first time visitors.

You are able to type in the URL: www.freecodecamp.org in your address bar to land on the homepage should you be "interested" in seeing the landing page.

We appreciate your feedback, happy coding.

@raisedadead raisedadead closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. status: waiting triage This issue needs help from moderators and users to reproduce and confirm its validity and fix. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants