Authentication extensions: suggestions #929
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There's a two-option CTA explained in the section that immediately follows the sentence in question, so we could consider removing the duplication.
Thanks for this, Kathryn. I'll let @zentron decide as the author and person managing the feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I’ve suggested a small change to copy, to remove adjacent duplication of the CTA.
The next bit occurred to me as I read the post, so I’ll share it just in case.
Would it be worth streamlining the CTA to email only? The public comments section may not be a great place to provide hints about customer authentication methods. I know it doesn’t open up customers to being hacked, but it feels like the kind of conversation best had over email.