Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Hold until GA: repoint kagent.dev navigation from 0.x to 1.x

Abierto Apto para principiantes
  • ¿Algo no está bien?
#521 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Rachael-Graham ya está trabajando en esto.

Desde el 29/9/2026.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
75/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
next.js, react, typescript
Área
content, documentation

Línea de trabajo

El trabajo está en el código fuente del sitio web, principalmente en src/components/footer.tsx, src/app/page.tsx, src/components/key-components.tsx, src/app/agents/[agentId]/page.tsx y archivos MDX del blog. Comience verificando los números de línea y rutas listados. Para cada enlace, decida la asignación 1.x o la resolución para colisiones/enlaces huérfanos. Agregue segmentos de versión explícitos a los enlaces sin versión. Finalmente, revise la lógica de redirección en next.config.mjs y documente la decisión para el comodín (catch-all).

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Do not action this before kagent 1.0 goes GA. The 1.0 release is an alpha, so kagent.dev's navigation deliberately keeps sending readers to the supported 0.x release. The links below look stale and are not. Repointing them early would land readers on alpha documentation.

This issue exists so the pinning is not mistaken for an oversight, and so the mapping is worked out once rather than re-derived at GA. Paths and line numbers were verified against main on 2026-09-23.

1. Repoint the 16 hardcoded documentation links

Sixteen links across three components hardcode 0.x/. The information architecture changed between versions, so this is not a find-and-replace: each link needs a mapping, and four of the sixteen need a decision instead.

Source 0.x path 1.x target
src/components/footer.tsx:21 introduction/installation setup/installation
src/components/footer.tsx:26 getting-started/quickstart collision — see below
src/components/footer.tsx:31 getting-started/first-agent collision — see below
src/components/footer.tsx:36 getting-started/first-mcp-tool get-started/your-first-mcp-tool
src/components/footer.tsx:48 introduction/what-is-kagent about/what-is-kagent
src/components/footer.tsx:53 concepts/architecture about/architecture
src/components/footer.tsx:58 concepts about
src/components/footer.tsx:63 supported-providers setup/model-providers
src/components/footer.tsx:85 examples/a2a-agents examples/a2a-agents
src/components/footer.tsx:90 examples/documentation examples/documentation-agent (renamed)
src/components/footer.tsx:95 examples/slack-a2a none — see below
src/components/footer.tsx:100 examples/discord-a2a none — see below
src/components/footer.tsx:132 resources/faq reference/faq
src/app/page.tsx:267 getting-started/quickstart collision — see below
src/app/page.tsx:683 getting-started/quickstart collision — see below
src/components/key-components.tsx:23 concepts about

Every target in that table was confirmed to exist. Two groups need a judgement call rather than a path:

  • quickstart and first-agent collapse into one 1.x page. 0.x ships Quick Start (install plus a first agent) and Creating your first agent (dashboard-based); 1.x ships only Your first agent. The footer lists both today. Either keep two entries, splitting them as setup/installation plus get-started/your-first-agent, or drop one.
  • slack-a2a and discord-a2a have no 1.x equivalent at all. Either remove the two footer entries or leave them on 0.x deliberately.

2. Pin the unversioned links

src/app/agents/[agentId]/page.tsx:110 points at /docs/kagent/getting-started/quickstart with no version segment and reaches 0.x only through the catch-all redirect below. It is the only unversioned link in an app component.

Eleven more sit in blog content and ride the same redirect:

File Count
src/blogContent/crewai-byo-agent.mdx 3
src/blogContent/deploy-kagent-with-agent-substrate.mdx 3
src/blogContent/human-in-the-loop-kagent.mdx 2
src/blogContent/is-pod-right-deployment-unit-ai-agent.mdx 1
src/blogContent/kgateway-guardrails.mdx 1
src/blogContent/reactive-agents-khook.mdx 1

Blog links carry a different consideration from navigation links: a post describes the release it was written against, so pinning each to 0.x/ explicitly is likely to be more correct than repointing it to 1.x.

src/config/navigation.json is unversioned throughout, but it is consumed only by scripts/check-links.mjs and never imported by app code. It is a link-checker fixture rather than a rendered navigation tree, so treat it separately.

3. Decide what the catch-all redirect does

next.config.mjs:34-38 sends every legacy unversioned /docs/kagent/* URL to 0.x/. The recommendation is to leave it on 0.x: those URLs were 0.x content, and the 1.x information architecture does not match path-for-path, so retargeting would land readers on 404s or on the wrong page.

The same decision covers two further redirects at next.config.mjs:19-28. Both hardcode 0.x destinations, for /docs/getting-started/configuring-providers and /docs/kagent/getting-started/tracing, and both sit above the catch-all deliberately, because the pages they name also changed section.

Done when

  • The 16 links resolve to 1.x, with the quickstart collision and the two orphaned examples decided rather than guessed
  • src/app/agents/[agentId]/page.tsx:110 carries an explicit version segment
  • The 11 blog links carry an explicit version segment, pinned to the release each post describes
  • The catch-all and the two redirects above it have a recorded decision, whether or not that decision changes them
  • No /docs/kagent/ link in src/ lacks a version segment, except the bare /docs/kagent version picker in navbar.tsx:42 and page.tsx:687
Lenguaje dominante
TypeScript
Estrellas
20
Forks
66
Merge medio
1 d 3 h
PR fusionados (30 d)
52

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kagent-dev/website

Todos los issues de kagent-dev/website

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.