Replace legacy /developer/ links with their final paths
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Run the provided rg -n --glob '*.mdx' '\(/developer/' command and review the 15 listed .mdx files. For each link, identify its final page path from docs.json redirects and confirm that page exists and is listed in navigation; use mint broken-links --check-redirects to validate. Done when all 35 links point directly to their final paths, including the bare /developer/bridges link.
Written by the indexing model from the issue text.
Description
35 internal links in 15 .mdx files still point at /developer/... paths. Each one works today only through a redirect in docs.json, almost all of them /developer/<section>/:slug* wildcards (for example /developer/contractkit/:slug* to /build/tools/libraries-sdks/contractkit/:slug*). The bare /developer/bridges relies on an exact redirect to /build/tools/bridges/bridges; the wildcard alone would send it to a page that doesn't exist. Readers get an extra redirect hop, mint broken-links --check-redirects cannot flag them while a wildcard matches, and they break if a wildcard is narrowed or removed. Each link should point at the final page, which must exist and be listed in docs.json navigation.
Found with:
rg -n --glob '*.mdx' '\(/developer/'
Files (link count), on main at 7f5d9bb5:
build/tools/dev-environments/hardhat.mdx(4)build/tools/dev-environments/remix.mdx(4)build/tools/explorers/overview.mdx(5)build/tools/libraries-sdks/contractkit/contracts-wrappers-registry.mdx(1)build/tools/libraries-sdks/contractkit/data-encryption-key.mdx(1)build/tools/libraries-sdks/contractkit/index.mdx(3)build/tools/libraries-sdks/contractkit/migrating-to-contractkit-v1.mdx(2)build/tools/libraries-sdks/contractkit/migrating-to-contractkit-v2.mdx(1)build/tools/libraries-sdks/contractkit/migrating-to-viem.mdx(1)build/tools/libraries-sdks/contractkit/setup.mdx(1)build/tools/libraries-sdks/contractkit/usage.mdx(1)build/tools/oracles/index.mdx(5)build/tools/overview/index.mdx(3)contribute-to-celo/release-process/smart-contracts.mdx(2)learn/network/overview.mdx(1)
Link targets: /developer/contractkit/migrating-to-viem (7), /developer/verify/celoscan (3), /developer/verify/blockscout (3), /developer/indexers/overview (3), /developer/verify/remix (2), /developer/verify/hardhat (2), /developer/explorers/block-explorers (2), /developer/explorers/analytics (2), /developer/contractkit/contracts-wrappers-registry (2), and one each of /developer/oracles/wit-oracle/ (trailing slash), /developer/oracles/wit-oracle, /developer/oracles/redstone, /developer/oracles/quex-oracles, /developer/oracles/band-protocol, /developer/explorers/overview, /developer/contractkit/usage, /developer/contractkit/setup, /developer/bridges/bridges and /developer/bridges (bare).
Found while reviewing #2366, which fixed the one /developer/ link on build/tools/libraries-sdks/contractkit/odis.mdx. Part of #2266.
- Dominant language
- MDX
- Stars
- 89
- Forks
- 396
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celo-org/docs
-
Add BlockVectra to the Celo mainnet RPC providers listPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
celo-org/docs#2362 · 1 comment ·
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
storytold/photocraft#15350 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
docker documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
VincenzoImp/openings-job-search#463 ·
Maintainers usually reply within 1 day
-
source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stephrobert/blog-roadmap#193 ·
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
pandas-dev/pandas#72163 ·
Maintainers usually reply within 2 days