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

Make the links in the README for the specific services point to *our* docs #637

Closed
jgeewax opened this issue Jun 2, 2015 · 4 comments
Closed

Make the links in the README for the specific services point to *our* docs #637

jgeewax opened this issue Jun 2, 2015 · 4 comments
Assignees
@stephenplusplus

Comments

@jgeewax
Copy link
Contributor

jgeewax commented Jun 2, 2015

If I click on Cloud Storage in the README, it sends me to the cloud storage landing page... I watched someone do this today, but they expected it to take them to the docs for cloud storage in node, not some marketing site......

Can we make our README point to the docs rather than the product pages? (Or add both so the main one is the docs, and in parens we have the link to the service overview?)
@jgeewax jgeewax added the docs label Jun 2, 2015
@stephenplusplus
Copy link
Contributor

Do you mean the top section under "This client supports the following Google Cloud Platform services:"? This is a style we're following across gcloud-* I believe. Given that these links look like a table of contents for the current document, I think it would be best to link to the matching section in the readme.

So, if you click "Google BigQuery" it will scroll you down to the BigQuery section which links to all possible interesting endpoints (cloud landing page, cloud docs, our docs).

@jgeewax
Copy link
Contributor Author

jgeewax commented Jun 4, 2015

I'm fine with that. I definitely don't want these linking off to cloud.google.com/ as it's ... basically a dead end for most people.

@stephenplusplus
Copy link
Contributor

Cool. I can send a PR to the other repos as well.

@jgeewax
Copy link
Contributor Author

jgeewax commented Jun 4, 2015 via email

@stephenplusplus stephenplusplus mentioned this issue Jun 8, 2015
Merged
This was referenced Jun 8, 2015
Merged
Merged
Merged
@sofisl sofisl mentioned this issue Oct 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Oct 11, 2022
@gcf-owl-bot
docs(node): support "stable"/"preview" release level (#1312) (#637)
a2b70ca
sofisl pushed a commit that referenced this issue Oct 13, 2022
@gcf-owl-bot @sofisl
docs(node): support "stable"/"preview" release level (#1312) (#637)
519846b
@sofisl sofisl mentioned this issue Nov 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Nov 11, 2022
@release-please
chore: release 3.1.0 (#637)
35befd6 
🤖 I have created a release \*beep\* \*boop\* 
---
## [3.1.0](https://www.github.com/googleapis/nodejs-dialogflow/compare/v3.0.0...v3.1.0) (2020-07-10)


### Features

* adds projectAgentEnvironmentPathTemplate and projectAgentEnvironmentUserSessionContextPathTemplate ([c204d9c](https://www.github.com/googleapis/nodejs-dialogflow/commit/c204d9cd7d9f121404b15783b8da5a451a671748))


### Bug Fixes

* typeo in nodejs .gitattribute ([#639](https://www.github.com/googleapis/nodejs-dialogflow/issues/639)) ([558aad8](https://www.github.com/googleapis/nodejs-dialogflow/commit/558aad81af74888516db9667f4a4e7b56cd3d3ba))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stephenplusplus stephenplusplus

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgeewax @stephenplusplus