Normalise session archive routes: mixed slug and folder-path URLs, duplicate session 14
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, typescript
调研方向
Start by reading the session notes frontmatter under website/docs/working-group/sessions/ and scripts/generate-sessions.js to see how slugs feed the carousel. Check the Docusaurus redirect configuration and CONTRIBUTING.md for existing conventions. Confirm the intended quarter and numbering for the conflicting sessions with maintainers, then update routes and redirects; done means all sessions use the stated URL shape, generated links pass the build's broken-link check, and the convention is documented.
由索引模型根据 Issue 内容生成。
描述
Page or section
website/docs/working-group/sessions/** (the working group session archive) and anything that links into it.
Issue description
The session archive serves two different URL shapes depending on whether a notes page carries a slug in frontmatter, and two folders claim the same session number.
Of the 21 sessions in the archive, 13 have a slug and are served at:
/docs/working-group/<quarter>/sessions/<NN-slug>/session-notes/
The other 8 have no slug, so Docusaurus falls back to the folder path, which strips the numeric prefix and keeps the literal sessions segment:
/docs/working-group/sessions/<quarter>/<slug>/session-notes/
The 8 without a slug:
| Quarter | Folder |
|---|---|
| q1-2026 | 09-community-builder-story |
| q1-2026 | 10-wallet-integration |
| q1-2026 | 11-open-source-docs |
| q1-2026 | 12-cardano-developer-pathway |
| q4-2025 | 01-kickoff-orientation |
| q4-2025 | 02-dev-opportunities |
| q4-2025 | 03-dev-environment-setup |
| q4-2025 | 04-essential-links |
Three more inconsistencies in the same tree:
- Number 14 is used twice.
q1-2026/14-CIP-68 NFT-Standardandq2-2026/14-sdk-repo-walkthroughboth claim session 14, and both are live pages. - Two slugs point at the wrong quarter.
q1-2026/07-contributing-intersectandq1-2026/08-open-clinic-1have slugs under/working-group/q1-2025/..., so their URLs say Q1 2025 while their folders say Q1 2026. - Folder names break their own convention.
14-CIP-68 NFT-Standardis capitalised and contains a space,Session-1/Session-2/Recordingare capitalised, and the quarter directory namedq1-2026holds documents whose URLs sayq1-2025.
Impact: any tool that derives archive links from the filesystem has to replicate Docusaurus's slug and number-prefix rules exactly. The scripts/generate-sessions.js generator that feeds the new session carousel on the landing page does exactly that, and its first version got one of the 8 fallbacks wrong; the build's broken-link check is the only thing that caught it, because a wrong route in the generated JSON fails the build rather than 404ing silently in production. Search results, cross-links between sessions, and any future redirect map inherit the same problem.
Nothing is broken for a reader today. Every existing route resolves.
Proposed change
Normalise the archive so a session's URL is a function of its quarter and number, and so a tool never has to guess:
- Add
slug: /working-group/<quarter>/sessions/<NN-slug>/session-notesto the 8 notes pages that lack one, so every session has a slug in the same shape. - Renumber one of the two
14s. The CIP-68 session predates the SDK walkthrough, so it likely needs a new number or a move into the quarter it actually belongs to. - Fix the
07and08slugs toq1-2026, or move those folders into aq1-2025directory, whichever matches when the sessions actually ran. - Rename
14-CIP-68 NFT-Standardto14-cip-68-nft-standard, and lowercaseSession-1,Session-2andRecordingfor consistency with the rest of the tree. - Add the old URLs to
@docusaurus/plugin-client-redirectsso inbound links and search results do not break when routes move. - Note the convention in
CONTRIBUTING.mdso new sessions land in the right shape.
Once every session carries a slug, scripts/generate-sessions.js can drop its path-derivation fallback and simply read the slug, which removes the class of bug entirely.
Checks
- I searched existing issues and discussions
- This is about documentation (not a feature request or bug)
- 主要语言
- TypeScript
- 星标
- 13
- 派生
- 24
- 平均合并
- 3 天 1 小时
- 30 天内合并 PR
- 34
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
IntersectMBO/developer-experience 的其他 Issue
-
documentation enhancement Low Priority
难度 1/5 1 小时以内 新手友好度 72/100
IntersectMBO/developer-experience#397 ·
维护者通常 2 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 72/100
IntersectMBO/developer-experience#376 ·
维护者通常 2 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 90/100
IntersectMBO/developer-experience#363 ·
维护者通常 2 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 88/100
IntersectMBO/developer-experience#362 ·
维护者通常 2 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 90/100
IntersectMBO/developer-experience#360 ·
维护者通常 2 天内回复
查看 IntersectMBO/developer-experience 的全部 Issue
相似的 Issue
-
bug parity
难度 2/5 1-3 小时 新手友好度 70/100
WenyuChiou/agent-board#1489 ·
维护者通常 1 天内回复
-
area: bazaar bug complexity: medium
难度 2/5 1-3 小时 新手友好度 74/100
accensa/x402-facilitator-stellar#779 ·
维护者通常 1 天内回复
-
bug good first issue P4 size:S web-ui
难度 2/5 半天 新手友好度 85/100
josephfung/curia#2600 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
cloudflare/partykit#444 ·