Open Bug 1762333 Opened 2 years ago Updated 2 years ago

Invalid Hyper links in Gecko Guides

Categories

(Websites :: wiki.mozilla.org, defect)

defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: woulfe68, Unassigned, NeedInfo)

References

()

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

For the Gecko home page in the section "Are You In The Right Place?"
click on a hyper link in sentence
Want to hack on Gecko? The [Developer Guide] is probably what you are looking for.

For the gecko getting started page click a hyperlink in the sentence
"The first step is to [download and build Firefox]"

Actual results:

For the Gecko home page in the section "Are You In The Right Place?"
was directed to:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide

For the gecko getting started page was redirected to
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions

Expected results:

I should of been directed to a site with documentation

Summary: Invalid Hyper link → Invalid Hyper links in Gecko Guides

Ref https://wiki.mozilla.org/MozillaWiki:About#Where_can_I_report_issues_with_wiki.mozilla.org.3F
"Where can I report issues with wiki.mozilla.org?

Technical issues should be reported via bugzilla. These include server or client-side errors, styling issues, problems with accounts or logging in, and feature requests.
Content issues should be addressed on the wiki itself using Talk/Discussion pages whenever possible."

This is a content issue.

That said I have flagged the WMO page referenced by this bug as "Outdated".

Spike

Group: websites-security

I have the information needed to update this and hope to have it corrected today.

I have updated the link in "Want to hack on Gecko? The [Developer Guide] is probably what you are looking for".

woulfe68 - please can you provide the link to the page where you saw "The first step is to [download and build Firefox]"

Flags: needinfo?(woulfe68)
You need to log in before you can comment on or make changes to this bug.