docs: Make authentication overview headings descriptive#635
Merged
Conversation
Swiftaxe
approved these changes
Jun 17, 2026
Swiftaxe
approved these changes
Jun 17, 2026
This was referenced Jun 17, 2026
This was referenced Jul 6, 2026
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
2 participants
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.
Makes the first heading on each top-level authentication page more descriptive so each page reads clearly out of context (for example, "Setup" becomes "Set up the authentication module"), and adds a
descriptionto the frontmatter of every page. Where a heading was lengthened, asidebar_labelkeeps the sidebar name short.Pages updated: Get started, Setup, The basics, Working with users, UI components, and Custom overrides.
First of four PRs splitting the same heading and description change across the authentication section. The providers, token managers, and legacy sections follow in separate PRs once this one is reviewed.
Part of #610