docs: Update Google Sign-In setup and configuration documentation#471
docs: Update Google Sign-In setup and configuration documentation#471
Conversation
| Sign in with Google requires a Google Cloud project linked to your organization's Google account. You also need platform-specific OAuth credentials depending on which platforms you target. | ||
|
|
||
| :::caution | ||
| You need to install the auth module before you continue, see [Setup](../../setup). |
There was a problem hiding this comment.
I believe we have to simplify this a bit. Sending people to another setup page with quite some stuff to grasp is making it harder. We want a smooth and simple how-to guide. Part of this is probably simplifying the setup page for installing the auth module.
| :::note | ||
| Right now, we have official support for iOS, Android, and Web for Google Sign In. | ||
| ::: | ||
| Sign in with Google requires a Google Cloud project linked to your organization's Google account. You also need platform-specific OAuth credentials depending on which platforms you target. |
There was a problem hiding this comment.
How do I setup a Google cloud project? If google has a great guide on this a link may suffice.
All these prerequisites should be in a section "prerequisites".
There was a problem hiding this comment.
Saw now that the "Cloud Project" is below. We need to rethink the structure here so the user understand the instructions for this follows below. This is like a lead sentence to setting these things up.
There was a problem hiding this comment.
This screenshot should focus on the enable button. Terms of Service, etc is irrelevant. Also make sure it is up to date with what this page looks like now.
This goes for all images. Focus on what the user needs to see to understand and follow.
…on setup, and match actual Serverpod 3.4.7 template
Problem
The Sign in with Google docs lacked screenshots for the Google Cloud Console setup steps, had no clear separation between what iOS, Android, and Web each require, and didn't explain key gotchas (YAML indentation, SHA-1 debug vs release mismatch, missing People API). There was also no troubleshooting page and the migration steps were incomplete.
Solution
serverpod create-migration), Firebase disambiguation note, and warnings for common mistakes.GoogleIdpConfigparameter reference table withpasswords.yamlkey column and environment variable equivalents section. Improved link text for accessibility.redirect_uri_mismatch, missing People API, token expiration on Web, and more.