Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン 初心者向け
  • 何か問題がありますか？
#521 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Rachael-Graham がすでに取り組んでいます。

2026年9月29日 から。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
75/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
next.js, react, typescript
領域
content, documentation

調査の方向性

作業はウェブサイトのソースコード内にあり、主に src/components/footer.tsx、src/app/page.tsx、src/components/key-components.tsx、src/app/agents/[agentId]/page.tsx、およびブログのMDXファイルにあります。まず、リストされている行番号とパスを確認してください。各リンクについて、1.xマッピングか、競合・孤立リンクの解決策を決定します。バージョン指定のないリンクには明示的なバージョンセグメントを追加します。最後に、next.config.mjs のリダイレクトロジックを確認し、キャッチオールに関する決定を文書化してください。

索引モデルが issue の本文から書いたものです。

説明

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
主要言語
TypeScript
スター
20
フォーク
66
平均マージ
1日 3時間
マージ済み PR（30日）
52

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

kagent-dev/website のほかの issue

kagent-dev/website の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。