chore(triage): record API-docs SSO as out of scope#226
Merged
Conversation
#216 asked whether the forum's SSO could improve the docs experience for logged-in members. It was a placeholder with no defined benefit, and it has been triaged and closed as out of scope: putting a session/SSO layer on the static docs page for an undefined payoff isn't worth it. This records the decision in .out-of-scope/docs-sso.md for dedup and institutional memory. > *This was generated by AI*
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#216 asked whether the forum's SSO could improve the docs experience for logged-in members. It was an open placeholder with no defined benefit, and it has been triaged and closed as out of scope: putting a session/SSO layer on the static docs page for an undefined payoff is not worth it.
This adds
.out-of-scope/docs-sso.mdso the decision and its reasoning persist for dedup and institutional memory, alongside the existinggzip-hijack-faithfulness.md. If a concrete member-facing reason for logged-in docs turns up later, the file gets deleted and the request goes back through triage fresh.Follow-up to the #216 triage close.