You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our docs run as a single Docusaurus instance with multiple sidebars (Ory Network, OEL, OSS, CIAM, B2B, …) that all reference the same shared pages under kratos/.... Docusaurus associates every doc with exactly one sidebar. That causes two problems:
Dual-listing breaks navigation. If a page is listed in two sidebars, one of them wins the association and is displayed no matter where the reader came from. Example: the Device authentication section (docs: add device authentication with PIN and biometrics guide #2673) was initially listed in both the Network and OEL sidebars; the OEL sidebar won, so clicking the entry from the Ory Network tree reshuffled the entire navigation into "Ory Enterprise License". This is not specific to that section — any dual-listed page behaves this way today.
Single-listing orphans the other deployment. The current convention (kratos feature pages are listed in the Network sidebar only — passkeys, one-time codes, organizations, now device authentication) avoids the reshuffle, but it means OEL readers have no OEL-context navigation for feature documentation at all: search results and deep links land them in the Network tree, surrounded by Network-specific navigation (Console, migration guides) that doesn't apply to self-hosted deployments.
Proposed fix
This is exactly what the migrated deployment structure in AGENTS.md solves: shared content lives in src/components/Shared/..., each deployment gets thin shell pages under docs/network/... / docs/oel/... with its own sidebar entry, and canonical URLs handle SEO. The kratos feature sections just haven't been migrated yet.
Suggestion: migrate the kratos authentication-method docs (passwordless + MFA, or the device authentication section as a pilot) to the deployment structure, so Network and OEL readers each keep a stable sidebar.
Problem
Our docs run as a single Docusaurus instance with multiple sidebars (Ory Network, OEL, OSS, CIAM, B2B, …) that all reference the same shared pages under
kratos/.... Docusaurus associates every doc with exactly one sidebar. That causes two problems:Proposed fix
This is exactly what the migrated deployment structure in
AGENTS.mdsolves: shared content lives insrc/components/Shared/..., each deployment gets thin shell pages underdocs/network/.../docs/oel/...with its own sidebar entry, and canonical URLs handle SEO. The kratos feature sections just haven't been migrated yet.Suggestion: migrate the kratos authentication-method docs (passwordless + MFA, or the device authentication section as a pilot) to the deployment structure, so Network and OEL readers each keep a stable sidebar.
Notes
🤖 Generated with Claude Code