The Gonka documentation site reorganised its cross-chain transfer section on 2026-06-13, pulling the two developer-facing integration guides out of the user walkthrough flow and into a dedicated dropdown. PR #1226, merged by @tcharchian, touched 9 files with 269 additions and 166 deletions.

What changed

Two pages — "Widget integration" and "Dashboard & tracker integration" — now sit under a new "Developer integration" dropdown beneath Cross-chain transfers. Before this change, "Widget integration" was a loose top-level entry and "Dashboard & tracker integration" was nested inside the Ethereum bridge section, two clicks apart from each other.

The PR also adds the Chinese translation for the new navigation label ("开发者集成"), keeping the English and Chinese navigation trees in sync rather than letting the ZH side drift behind.

The stated intent in #1226 is to separate developer-facing API and integration material from the user-facing bridge guides, which had grown intertwined as the bridge docs expanded.

Why it matters

A developer arriving at the docs to wire up the bridge widget or the dashboard tracker API previously had to hunt: one reference sat at the top level, the other was buried under the Ethereum bridge walkthrough. Grouping both under a single "Developer integration" heading puts the two technical references next to each other, so finding the dashboard integration page no longer means reading through the end-user bridge instructions first.

The split cuts the other way too. The user-facing bridge guides — how to deposit, withdraw, and move funds through the dashboard UI — stay uncluttered for non-technical readers who never needed the API details in the first place.

Tradeoffs and follow-ups

The PR carries a test plan rather than a completed verification: rendering the navigation with mkdocs serve in both English and Chinese, and confirming the "Developer integration" dropdown expands with both sub-pages. These were listed as open checks at merge time, so the rendered result is worth a glance on the next docs deploy.