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.

Sign up for GitHub

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

Jump to bottom

tour: link to more resources throughout all content #13390

Open
paupin2 opened this issue Nov 24, 2015 · 5 comments
Open

tour: link to more resources throughout all content #13390

paupin2 opened this issue Nov 24, 2015 · 5 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@paupin2
Copy link

paupin2 commented Nov 24, 2015

Context: https://tour.golang.org/concurrency/5

It would be very useful to have a "Would you like to know more?" link in the description to the documentation, in this case https://golang.org/ref/spec#Select_statements
@rsc rsc added this to the Go1.6Maybe milestone Dec 28, 2015
@rsc
Copy link
Contributor

rsc commented Jan 6, 2016

@campoy?

@campoy
Copy link
Contributor

campoy commented Jan 8, 2016

This might end up making us add links to the specs on every single page of the tour.

We already point to the specs at the end of the tour (http://tour.golang.org/concurrency/11)

What do you think, @adg?

@adg
Copy link
Contributor

adg commented Jan 11, 2016

I think it doesn't hurt to add more links. Probably we should be adding more links to definitions and resources throughout the tour.

I'll rename this issue to track the general issue of adding such links.

@adg adg changed the title tour: Add link to documentation tour: link to more resources throughout all content Jan 11, 2016
@adg
Copy link
Contributor

adg commented Jan 11, 2016

Here's an attempt at policy:

  • When a language concept is introduced, link to the corresponding section of the spec.
  • When a standard library package or name is mentioned, link to the relevant godoc.

@omeid
Copy link

omeid commented Jan 29, 2016

Some links to Effective Go would be also nice. Learned many things in Effective Go the hard way.

@rsc rsc modified the milestones: Unplanned, Go1.6Maybe Feb 16, 2016
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
6 participants
@rsc @paupin2 @omeid @campoy @adg @seankhliao