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

x/pkgsite: redirect feedback - tracking issue #39144

julieqiu opened this issue May 19, 2020 · 3 comments

x/pkgsite: redirect feedback - tracking issue #39144

julieqiu opened this issue May 19, 2020 · 3 comments


Copy link

@julieqiu julieqiu commented May 19, 2020

This is an umbrella issue to keep track of issues related to redirecting traffic from to

Issues related to this topic:

  • #36747: open source
  • #36811: support viewing a package@master
  • #36865: examples missing playground links
  • #36929: add support for bookmarklet to navigate from repository to doc
  • #36982: serve status badge similar to
  • #37002: automatically fetch a requested package if it does not exist on
  • #37099: support package owner-initiated redirect from to
  • #37863: missing source files listing
  • #38056: automatically link RFCs in package documentation
  • #38763: incorrect rendering of fixed-size unicode box-drawing characters
  • #38892: slower loads than
  • #38986: missing links to source code for
  • #39270: documentation misparsed as an anchor
  • #39529: missing documentation headings/anchors

At the moment, our priority is to work towards open sourcing (#36747) and to address design feedback. We will plan to address the issues above before redirecting traffic from to

/cc @jba @spf13 @fflewddur @Joanne881107

Copy link

@tooolbox tooolbox commented May 22, 2020

Sounds fantastic @julieqiu and it's really awesome how much the feedback is being taken into account on this.

A suggestion I have on the redirect is to do it a little like Go Modules: first opt-in, then opt-out, then full switchover. Right now you have the ability to opt-in to always redirect using a cookie, so for the next stage you could redirect unless a specific cookie is set.

I think this would be a very gentle way of going about it, and might spark a final round of useful feedback as the whole community adapts to the change (while still being able to browse the legacy version).

If the percentage of traffic opting-in to the redirect is very high, this suggestion may be unnecessary, but I wanted to throw it out there.

Copy link
Contributor Author

@julieqiu julieqiu commented May 25, 2020

That's great suggestion - thanks @tooolbox! We'll definitely consider doing something like that, once we get closer to being ready to redirect traffic.

Copy link
Contributor Author

@julieqiu julieqiu commented Jul 29, 2020

Closing this issue in favor of using milestone pkgsite/

@julieqiu julieqiu closed this Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.