Normalise session archive routes: mixed slug and folder-path URLs, duplicate session 14
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github, typescript
- Área
- documentation
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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)
- Lenguaje dominante
- TypeScript
- Estrellas
- 13
- Forks
- 24
- Merge medio
- 3 d 1 h
- PR fusionados (30 d)
- 34
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de IntersectMBO/developer-experience
-
documentation enhancement Low Priority
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
IntersectMBO/developer-experience#397 ·
Los mantenedores suelen responder en 2 días
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IntersectMBO/developer-experience#376 ·
Los mantenedores suelen responder en 2 días
-
documentation pinned
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
IntersectMBO/developer-experience#363 ·
Los mantenedores suelen responder en 2 días
-
documentation pinned
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
IntersectMBO/developer-experience#362 ·
Los mantenedores suelen responder en 2 días
-
documentation pinned
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
IntersectMBO/developer-experience#360 ·
Los mantenedores suelen responder en 2 días
Todos los issues de IntersectMBO/developer-experience
Issues similares
-
[analytics-core] getQueryParams does not decode `+` as space and truncates values containing `=`Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
amplitude/Amplitude-TypeScript#2179 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
ci good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
TMHSDigital/GH-Arcade#111 ·
-
AsnIntegerConverter.toASN coerces strings with +value, rounding integers outside safe-integer rangeAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
PeculiarVentures/asn1-schema#189 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 4 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100