Summary
During a navigation audit of developers.uniswap.org/docs (May 2026), I found several structural issues that block developer onboarding.
Structural Gaps
- No inline API reference — API docs live on a separate domain (
api-docs.uniswap.org) with no integrated search or navigation inside the main developer portal.
- Missing v3 → v4 migration guide — No comparative guide for devs migrating existing integrations.
- Hook guides lack production patterns — The Counter Hook example is too basic; intermediate patterns (dynamic fees, oracles, limit orders) and end-to-end deployment guides (address derivation, bit flags, CREATE2) are missing.
- No docs bug-reporting channel — The official feedback Google Form collects role/experience data but has no field to report broken links or documentation errors.
Suggested Fixes
- Integrate API reference pages directly into
developers.uniswap.org/docs/api/reference.
- Add a
[Docs Bug] issue template to this repo.
- Provide a "Report a docs issue" link in the portal footer.
Environment
Summary
During a navigation audit of
developers.uniswap.org/docs(May 2026), I found several structural issues that block developer onboarding.Structural Gaps
api-docs.uniswap.org) with no integrated search or navigation inside the main developer portal.Suggested Fixes
developers.uniswap.org/docs/api/reference.[Docs Bug]issue template to this repo.Environment