x/website: offline tour broken links

[crisman]

While trying to fix offline tour links other go.dev resources (golang/tour#1463 & golang/tour#1473) I put in golang/website#213 which updated URLs to work offline by adding https://go.dev/ prefixes.

I later noticed this commit:

commit f81f4f7f21d45f2e62f8dbcf84e0fd5d7b2785a3
Author: Russ Cox rsc@golang.org
Date: Fri Jan 14 12:53:28 2022 -0500

_content: remove some https://go.dev/ prefixes in links

The site is served at both go.dev and golang.google.cn.
In China, only golang.google.cn can serve, so we try to use
relative links to avoid pointing users to the copy they can't access.

Periodically we have to remove prefixes that have crept in.
This commit applies today's round of that.

Which points out a third place these URLs need to work and a reason and policy to use relative URLs.

I think we need the local tour binary to get a handler update to allow for redirect of /pkg/, /blog/, /doc/, /talks/, /cmd/, & /.

There is already a handler for / which redirects to the tour start point which might should stay that way.

Does anyone see an issue with adding redirect handlers to the offline tour?

Does anyone have a input on changing or not of the / handler?

[cagedmantis]

cc @golang/tools-team

[jamalc]

@crisman, I'd like to get a clearer picture of what this update involves. My understanding is that the tour is served by cmd/golangorg in the x/website module. Can you point me to the local tour binary?

🤦 I see it now. We should include those handlers in the tour binary but keep the / handler in place.

[crisman]

Rereading my original post, perhaps a bit more detail on my last question:

Does anyone have a input on changing or not of the / handler?

The current internal/tour/local.go starts a local http server and then a browser sent to (by default) http://127.0.0.1:3999 which then (in the / handler) is redirected to http://127.0.0.1:3999/tour/.

An option would be to change the url to add a suffix if "/tour/" and then the default action for the / handler could be to redirect to https://go.dev/ which would allow the top left GO link on every tour page to work.

The down side is that if we make that change then a user manually visiting http://127.0.0.1:3999 (which they may have in memory or a bookmark) would not get the local tour, but the main go site.

I like the idea of changing the url & the / hander. Does anyone have any reasons to add to the for or against lists for changing the / handler?