readme: point service links to readme intro documentation #915
Conversation
googlebot
added
the
cla: yes
|
I don't really mind either way, but where do users get linked to the web service docs? @jgeewax |
|
We can add a link to those... but keep in mind that the links we currently have aren't to the docs... they're to the crappy marketing-focused landing page... If someone makes it all the way to our README, it's super unlikely they want to go to that marketing page. Maybe add in parens "(Google service documentation)" -> https://cloud.google.com/storage/docs/json_api/v1/ ? |
|
Yes I like that. @stephenplusplus you want to change this PR or shall I do that? |
|
I can add it in. Were you thinking (Google service documentation) would go in the header, or as one of the links in the service paragraph? I'm partial to keeping it with the rest of the links, leaving the header service links as a table of contents to skip around the readme. Google Cloud DatastoreGoogle Cloud Datastore (service API docs) is a fully managed, schemaless database for storing non-relational data. Cloud Datastore automatically scales with your users and supports ACID transactions, high availability of reads and writes, strong consistency for reads and ancestor queries, and eventual consistency for all other queries. See the Google Cloud Datastore docs for more details on how to activate Cloud Datastore for your project. See the gcloud-python API datastore documentation to learn how to interact with the Cloud Datastore using this Client Library. |
|
I'm all for that, but could we swap the order of the last two "See.."
paragraphs? And change "Google Cloud Datastore docs" to "Official Google
Cloud Datastore documentation" ?
|
stephenplusplus
force-pushed
the
master
branch
3 times, most recently
from
28c6003
to
af07138
Compare
|
LGTM |
readme: point service links to readme intro documentation
Hey, guys!
RE: googleapis/google-cloud-node#637
@jgeewax thinks it makes more sense to point the Service links (Google Cloud Datastore and Google Cloud Storage) to their respective sections in the readme.