Normalise session archive routes: mixed slug and folder-path URLs, duplicate session 14
I maintainer di solito rispondono entro 2 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Documentazione
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- github, typescript
- Ambito
- documentation
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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)
- Lingua principale
- TypeScript
- Stelle
- 13
- Fork
- 24
- Merge medio
- 3g 1h
- PR unite (30g)
- 34
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di IntersectMBO/developer-experience
-
documentation enhancement Low Priority
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
IntersectMBO/developer-experience#397 ·
I maintainer di solito rispondono entro 2 giorni
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
IntersectMBO/developer-experience#376 ·
I maintainer di solito rispondono entro 2 giorni
-
documentation pinned
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
IntersectMBO/developer-experience#363 ·
I maintainer di solito rispondono entro 2 giorni
-
documentation pinned
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
IntersectMBO/developer-experience#362 ·
I maintainer di solito rispondono entro 2 giorni
-
documentation pinned
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
IntersectMBO/developer-experience#360 ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di IntersectMBO/developer-experience
Issue simili
-
bug parity
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
WenyuChiou/agent-board#1489 ·
I maintainer di solito rispondono entro 1 giorno
-
area: bazaar bug complexity: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
accensa/x402-facilitator-stellar#779 ·
I maintainer di solito rispondono entro 1 giorno
-
bug good first issue P4 size:S web-ui
Difficoltà 2/5 Mezza giornata Idoneità per principianti 85/100
josephfung/curia#2600 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
cloudflare/partykit#444 ·