ory / ory/docs

Shared kratos pages can only belong to one sidebar — OEL readers lose navigation context

Open
#2,674 0 comments 0 reactions 1 assignee View on GitHub

@hperl is already working on this.

Since Jul 12, 2026.

Dominant language
TypeScript
Stars
161
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

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:

  1. 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 (#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.
  2. 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.

Notes

  • Behavior predates #2673 — the old device binding page was dual-listed and showed the OEL sidebar even when reached from the Network tree.
  • Interim mitigation applied in #2673: the device authentication section is Network-only, matching the sibling convention.
  • Related: #2323 (self-hosted section missing specific pages) — same underlying tension: the OEL sidebar has no systematic way to carry the shared feature docs.

🤖 Generated with Claude Code

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.