We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Consolidate the wiki: canonical Coding Standards, merged Architecture, split Provider Setup Restructure the wiki into one coherent, audience-grouped set with a single home for each fact. - New Coding-Standards page: the one canonical statement of the architecture, comment/documentation (#864), and object-oriented rules; the repo's CLAUDE.md and CONTRIBUTING.md now point here instead of restating them. - Merged the two stale, mutually-overlapping Architecture pages into one, re-based on the current module-DAG reality (the old pages claimed the module split was "not pursued" and that no IPluginServiceRegistrator existed — both were wrong and contradicted docs/ARCHITECTURE.md). Cites modules and types, never file:line, so it cannot drift on a move again. - Split Provider-Setup (1172 lines, ~73% not provider-specific) into Provider Setup (recipes) + a new Hardening & Options Reference; folded the security- control narrative into the Security Model. Every moved section left a pointer. - Merged Release-Policy + Release-QA-Checklist into Releasing (renamed the per-release ladder to "release promotion ladder" to end the Beta-rung name collision); merged OpenSSF-Best-Practices + Maturity-Map into Security & Maturity Self-Assessment. Old slugs kept as redirect stubs. - Rebuilt the sidebar into four audience groups (Getting started / How it works / Security / Standards & process). Fixed the broken anchors, corrected the beta publish-trigger to the daily scheduler (it is not "every merge"), de-referenced the design records to module/type names, and trimmed Home's README duplication.
Migrate design, process, and provider docs from the repo into the wiki Add wiki pages for the per-provider setup guides, the delivery-pipeline threat model, the release/rollback/review-gate/QA process docs, the DORA delivery metrics, the OpenSSF best-practices assessment, the single-logout and SSO-only-login design notes, and an architecture-internals code map. Retarget every internal link: cross-doc references now point at wiki pages, references to files that stay in the repo point at full github blob URLs, and provider screenshots point at raw.githubusercontent URLs. Add a grouped navigation to Home (user docs / architecture & security / process & release / design records), cross-link Login-Flow and Architecture with the new Architecture-Internals map, and cross-link Security-Model with Threat-Model.
Add a Login Flow page describing both sign-in flows end to end Walk an OpenID Connect and a SAML 2.0 sign-in through the four shared stages (challenge, identity provider, callback validation, session mint), each with a sequence sketch, and cover role mapping, canonical-link account resolution, self-service linking, edge rate limiting, and Quick Connect for non-web clients. Cross-link each validation step to the Security Model rather than restating it, and add the page to the Home Pages list.