Shared kratos pages can only belong to one sidebar — OEL readers lose navigation context
@hperl がすでに取り組んでいます。
2026年7月12日 から。
評価
この issue はまだ評価されていません。
説明
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:
- 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.
- 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
- 主要言語
- TypeScript
- スター
- 161
- フォーク
- 1.9k
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ory/docs のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
good first issue help wanted upstream
難易度 1/5 1〜3時間 初心者へのやさしさ 72/100
-
bug
難易度 1/5 1時間未満 初心者へのやさしさ 78/100
-
good first issue help wanted upstream
難易度 1/5 1〜3時間 初心者へのやさしさ 72/100
-
good first issue help wanted upstream
難易度 1/5 1時間未満 初心者へのやさしさ 58/100
似ている issue
-
module-request
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
appandflow/stim#1604 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
lingdojo/kana-dojo#31060 · コメント 1 件 · リアクション 5 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
paperclipai/paperclip#14173 ·
メンテナーはふだん 1 日以内に返信
-
needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信