gdrive: update docs

Author: maxhora

public/static/docs/command-reference/remote/add.md

@@ -194,50 +194,12 @@ $ dvc remote add myremote "azure://"
 
 ### Click for Google Drive
 
-Since Google Drive has tight API usage quotas, creation and configuration of
-your own `Google Project` is required:
-
-1.  Log into the [Google Cloud Platform](https://console.developers.google.com)
-    account.
-2.  Create `New Project` or select available one.
-3.  Click `ENABLE APIS AND SERVICES` and search for `drive` to enable
-    `Google Drive API` from search results.
-4.  Navigate to
-    [All Credentials](https://console.developers.google.com/apis/credentials)
-    page and click `Create Credentials` to select `OAuth client ID`. It might
-    ask you to setup a product name on the consent screen.
-5.  Select `Other` for `Application type` and click `Create` to proceed with
-    default `Name`.
-6.  `client id` and `client secret` should be showed to you. Use them for
-    further DVC's configuration.
+> 💡 Before adding a Google Drive remote, be sure to check
+> [Setup Google Drive Remote](/doc/user-guide/setup-google-drive-remote) user
+> guide.
 
 ```dvc
-$ dvc remote add myremote gdrive://root/my-dvc-root
-$ dvc remote modify myremote gdrive_client_id my_gdrive_client_id
-$ dvc remote modify myremote gdrive_client_secret gdrive_client_secret
-```
-
-On first usage of the remote you will be prompted to visit an access token
-generation URL via browser. It will ask you to log into the Google account
-associated with the Google Drive you want to use as remote. The login process
-will guide you through the granting of the required access permissions.
-
-On successful access token generation, the token data will be cached in a
-Git-ignored directory (located in `.dvc/tmp/gdrive-user-credentials.json`).
-
-> 💡 Do not share the token data with anyone else to prevent unauthorized access
-> to your Google Drive.
-
-**Support for shared drives**
-
-For this, you need to obtain the directory ID and use it as part of URL passed
-to DVC. This ID can be found in your web browser address bar when the shared
-drive is opened. For example, for the URL
-`https://drive.google.com/drive/folders/0AIac4JZqHhKmUk9PDA`, use
-`0AIac4JZqHhKmUk9PDA` as ID:
-
-```dvc
-$ dvc remote add myremote gdrive://0AIac4JZqHhKmUk9PDA/my-dvc-root
+$ dvc remote add -d myremote gdrive://root/path/to/dir
 ```
 
 </details>

public/static/docs/sidebar.json

@@ -159,7 +159,8 @@
       {
         "label": "Anonymized Usage Analytics",
         "slug": "analytics"
-      }
+      },
+      "setup-google-drive-remote"
     ]
   },
   {

public/static/docs/user-guide/setup-google-drive-remote.md

@@ -0,0 +1,90 @@
+# Setup Google Drive remote
+
+To setup Google Drive remote you should
+[create and configure Google Project](#create-and-configure-google-project) if
+you don't have one yet.
+
+## Create and Configure Google Project
+
+Since Google Drive has tight API usage quotas, one time creation and
+configuration of your own `Google Project` is required. Required `client_id` and
+`client_secret` can be generated only once and shared with other DVC users in
+your organization.
+
+1.  Log into the [Google Cloud Platform](https://console.developers.google.com)
+    account.
+2.  Create `New Project` or select available one.
+3.  From the left sidebar menu select `APIs & Services`->`Dashboard` and click
+    `ENABLE APIS AND SERVICES` to search for `drive` to enable
+    `Google Drive API` from search results.
+
+    ![](/static/img/gdrive-enable-apis-and-services.png)
+
+4.  From the left sidebar menu select `APIs & Services`->`Credentials` and click
+    `Create Credentials` to select `OAuth client ID`. It might ask you to setup
+    a product name on the consent screen. Complete all required steps.
+
+    ![](/static/img/gdrive-create-credentials.png)
+
+5.  Select `Other` for `Application type` and click `Create` to proceed with
+    default `Name`.
+6.  `client id` and `client secret` should be showed to you. Use them for
+    further DVC's configuration.
+
+```dvc
+$ dvc remote add -d myremote gdrive://path # see URL format section below
+$ dvc remote modify myremote gdrive_client_id my_gdrive_client_id
+$ dvc remote modify myremote gdrive_client_secret gdrive_client_secret
+```
+
+⚠️ It is safe to share `client_id` and `client_secret` at least with your
+teammates or inside organization. These credentialds are used to
+[retrieve authorization token](https://developers.google.com/identity/protocols/OAuth2)
+and
+[authenticate your application](https://developers.google.com/drive/api/v2/about-auth)
+to Google. Credentialds don't give access to your Google Drive storage. But
+Google limits global number of queires per each `client_id` and uncontrolled
+usage of your `cliend_id` by outer world can lead to
+[reaching the allowed Google API usage limits](https://developers.google.com/drive/api/v2/handle-errors?hl=ro#quota).
+
+## Google Drive remote URL format
+
+Remote URL can contain `root` which is an alias of your topmost Google Drive
+directory. To point the remote to the path under Google Drive's `root`
+directory:
+
+```dvc
+$ dvc remote add -d myremote gdrive://root/path/to/dir
+```
+
+As alternative, you can obtain unique `Google Drive id` of your desired remote
+directory and use it as `base` remote path in URL:
+
+```dvc
+$ dvc remote add -d myremote gdrive://0AIac4JZqHhKmUk9PDA/path/to/dir
+```
+
+To obtain `Google Drive id` of remote directory navigate inside that directory
+in your web browser with opened Google Drive and find `Google Drive id` in
+address bar. For example, for the URL
+
+```dvc
+https://drive.google.com/drive/folders/0AIac4JZqHhKmUk9PDA
+```
+
+the `id` will be equal to `0AIac4JZqHhKmUk9PDA`.
+
+`Shared Team Drive` can be referenced by `Google Drive id` in the similar way.
+
+## Authorization
+
+On first usage of remote you will be prompted to visit access token generation
+link in browser. It will ask you to log into Google account associated with
+Google Drive, which you want to use as DVC's remote. Login process will guide
+you through granting Google Drive access permissions to the used Google Project.
+
+On successful access token generation token data will be cached in git ignored
+directory with path `.dvc/tmp/gdrive-user-credentials.json`.
+
+⚠️ Do not share token data with anyone else to prevent unauthorized access to
+your Google Drive.