docs: content update#785
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR restructures the ZetaChain documentation site by removing advanced chain-specific and protocol guides, consolidating tutorials to staking only, rebranding developer sections from "Build" to "Architecture," and pivoting the getting-started narrative from cross-chain universal apps toward standard EVM smart contract development. ChangesDocumentation Restructuring and Architecture-First Navigation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pages/about/overview.en-US.mdx`:
- Line 13: Replace the unhyphenated compound modifier "~5 second blocks" with
the hyphenated form "~5-second blocks" in the text (look for the phrase "~5
second blocks" in the content, e.g., in the sentence beginning "The chain has ~5
second blocks...") so the modifier is grammatically correct.
- Around line 9-11: Update the hardcoded links in the MDX content so they use
the canonical domain https://www.zetachain.com; specifically replace the URLs
for the link texts "Cosmos SDK", "CometBFT", and "Cosmos EVM" (and any other
hardcoded links in the same file mentioned in the comment) with their canonical
https://www.zetachain.com/... counterparts, ensuring each href begins with
https://www.zetachain.com/ and preserving the visible link text and path
segments.
In `@src/pages/about/overview.zh-CN.mdx`:
- Around line 2-30: Replace the English copy in this zh-CN locale file by
localizing the frontmatter fields and body into Simplified Chinese: update the
title and description frontmatter values (the "title:" and "description:"
fields) to Chinese, and translate the entire body paragraph(s) including the
opening description that starts with "ZetaChain is a Proof of Stake Layer 1
blockchain..." plus the "Explore" section items and the third-party disclaimer
into fluent Simplified Chinese while keeping heroImgUrl and heroImgWidth
unchanged; ensure links and markdown structure are preserved and that Chinese
punctuation/terminology is used consistently for UX.
- Around line 9-11: Replace all hardcoded external links in the MDX page with
the canonical www.zetachain.com domain: change the occurrences of
https://docs.cosmos.network/, https://docs.cometbft.com/, and
https://evm.cosmos.network/ (found around the block showing Cosmos SDK /
CometBFT / Cosmos EVM and additionally in the section referenced at lines 19-23)
to their corresponding https://www.zetachain.com/... canonical URLs; ensure
every hardcoded URL in src/pages/about/overview.zh-CN.mdx uses
https://www.zetachain.com as the base and update any remaining links elsewhere
in that file to follow the same rule so no MDX links point to non-canonical
domains.
- Line 13: Replace the unhyphenated compound in the sentence containing "The
chain has ~5 second blocks with instant finality, an EIP-1559 fee market," by
changing "~5 second blocks" to "~5-second blocks" so the phrase reads "The chain
has ~5-second blocks with instant finality, an EIP-1559 fee market,"; update
this exact string in the src/pages/about/overview.zh-CN.mdx content.
In `@src/pages/start/app.zh-CN.mdx`:
- Around line 2-3: The zh-CN locale page has English frontmatter and content;
restore Chinese localization by replacing the frontmatter fields (title,
description) with Chinese equivalents and translating the MDX body into Chinese;
update the frontmatter keys in app.zh-CN.mdx (title, description) to Chinese
strings like "智能合约" and a Chinese description, and translate all English body
headings, paragraphs and code comments into Simplified Chinese to match the
locale; apply the same fix pattern to the other affected locale files referenced
(lines 6-16) to ensure consistency across zh-CN pages.
In `@src/pages/start/build.zh-CN.mdx`:
- Around line 2-3: The zh-CN localized page has English frontmatter fields
"title" and "description" and English body copy; replace those with Chinese
translations and localize the entire MDX body (including headings, paragraphs,
code comments and any UI strings). Update the "title" and "description"
frontmatter to Chinese equivalents, and scan the rest of the document for
remaining English (lines noted around the top and also lines 6-18) to translate
them into Simplified Chinese so the page is fully localized.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4679dd32-2e35-446b-afd6-31da4a525137
📒 Files selected for processing (99)
src/pages/about/overview.en-US.mdxsrc/pages/about/overview.zh-CN.mdxsrc/pages/developers/_meta.en-US.jsonsrc/pages/developers/_meta.zh-CN.jsonsrc/pages/developers/architecture/_meta.en-US.jsonsrc/pages/developers/architecture/_meta.zh-CN.jsonsrc/pages/developers/architecture/observers.en-US.mdxsrc/pages/developers/architecture/observers.zh-CN.mdxsrc/pages/developers/architecture/whitelisting.en-US.mdxsrc/pages/developers/architecture/whitelisting.zh-CN.mdxsrc/pages/developers/chains/_meta.en-US.jsonsrc/pages/developers/chains/_meta.zh-CN.jsonsrc/pages/developers/chains/bitcoin.en-US.mdxsrc/pages/developers/chains/bitcoin.zh-CN.mdxsrc/pages/developers/chains/evm.en-US.mdxsrc/pages/developers/chains/evm.zh-CN.mdxsrc/pages/developers/chains/functionality.en-US.mdxsrc/pages/developers/chains/functionality.zh-CN.mdxsrc/pages/developers/chains/list.en-US.mdxsrc/pages/developers/chains/list.zh-CN.mdxsrc/pages/developers/chains/solana.en-US.mdxsrc/pages/developers/chains/solana.zh-CN.mdxsrc/pages/developers/chains/sui.en-US.mdxsrc/pages/developers/chains/sui.zh-CN.mdxsrc/pages/developers/chains/ton.en-US.mdxsrc/pages/developers/chains/ton.zh-CN.mdxsrc/pages/developers/chains/zetachain.en-US.mdxsrc/pages/developers/chains/zetachain.zh-CN.mdxsrc/pages/developers/evm/_meta.en-US.jsonsrc/pages/developers/evm/_meta.zh-CN.jsonsrc/pages/developers/evm/cctx.en-US.mdxsrc/pages/developers/evm/cctx.zh-CN.mdxsrc/pages/developers/evm/gas.en-US.mdxsrc/pages/developers/evm/gas.zh-CN.mdxsrc/pages/developers/evm/gateway.en-US.mdxsrc/pages/developers/evm/gateway.zh-CN.mdxsrc/pages/developers/evm/index.zh-CN.mdxsrc/pages/developers/evm/throughput.en-US.mdxsrc/pages/developers/evm/throughput.zh-CN.mdxsrc/pages/developers/evm/zrc20.en-US.mdxsrc/pages/developers/evm/zrc20.zh-CN.mdxsrc/pages/developers/protocol/_meta.en-US.jsonsrc/pages/developers/protocol/_meta.zh-CN.jsonsrc/pages/developers/protocol/evm.en-US.mdsrc/pages/developers/protocol/evm.zh-CN.mdsrc/pages/developers/protocol/solana.en-US.mdsrc/pages/developers/protocol/solana.zh-CN.mdsrc/pages/developers/protocol/sui.en-US.mdsrc/pages/developers/protocol/sui.zh-CN.mdsrc/pages/developers/protocol/ton.en-US.mdsrc/pages/developers/protocol/ton.zh-CN.mdsrc/pages/developers/standards/_meta.en-US.jsonsrc/pages/developers/standards/_meta.zh-CN.jsonsrc/pages/developers/standards/nft.en-US.mdxsrc/pages/developers/standards/nft.zh-CN.mdxsrc/pages/developers/standards/overview.en-US.mdxsrc/pages/developers/standards/overview.zh-CN.mdxsrc/pages/developers/standards/token.en-US.mdxsrc/pages/developers/standards/token.zh-CN.mdxsrc/pages/developers/tutorials/_meta.en-US.jsonsrc/pages/developers/tutorials/_meta.zh-CN.jsonsrc/pages/developers/tutorials/call.en-US.mdxsrc/pages/developers/tutorials/call.zh-CN.mdxsrc/pages/developers/tutorials/frontend.en-US.mdxsrc/pages/developers/tutorials/frontend.zh-CN.mdxsrc/pages/developers/tutorials/hello.en-US.mdxsrc/pages/developers/tutorials/hello.zh-CN.mdxsrc/pages/developers/tutorials/intro.en-US.mdxsrc/pages/developers/tutorials/intro.zh-CN.mdxsrc/pages/developers/tutorials/messaging.en-US.mdxsrc/pages/developers/tutorials/messaging.zh-CN.mdxsrc/pages/developers/tutorials/solana.en-US.mdxsrc/pages/developers/tutorials/solana.zh-CN.mdxsrc/pages/developers/tutorials/sui-withdraw-and-call.en-US.mdxsrc/pages/developers/tutorials/sui-withdraw-and-call.zh-CN.mdxsrc/pages/developers/tutorials/sui.en-US.mdxsrc/pages/developers/tutorials/sui.zh-CN.mdxsrc/pages/developers/tutorials/swap.en-US.mdxsrc/pages/developers/tutorials/swap.zh-CN.mdxsrc/pages/reference/_meta.en-US.jsonsrc/pages/reference/_meta.zh-CN.jsonsrc/pages/reference/cli.en-US.mdxsrc/pages/reference/cli.zh-CN.mdxsrc/pages/reference/localnet.en-US.mdxsrc/pages/reference/localnet.zh-CN.mdxsrc/pages/reference/mcp.en-US.mdxsrc/pages/reference/mcp.zh-CN.mdxsrc/pages/reference/registry.en-US.mdxsrc/pages/reference/registry.zh-CN.mdxsrc/pages/reference/toolkit.en-US.mdxsrc/pages/reference/toolkit.zh-CN.mdxsrc/pages/start/_meta.en-US.jsonsrc/pages/start/_meta.zh-CN.jsonsrc/pages/start/app.en-US.mdxsrc/pages/start/app.zh-CN.mdxsrc/pages/start/build.en-US.mdxsrc/pages/start/build.zh-CN.mdxsrc/pages/start/zetachain.en-US.mdxsrc/pages/start/zetachain.zh-CN.mdx
💤 Files with no reviewable changes (81)
- src/pages/reference/localnet.en-US.mdx
- src/pages/developers/chains/_meta.en-US.json
- src/pages/developers/evm/gateway.en-US.mdx
- src/pages/reference/mcp.en-US.mdx
- src/pages/developers/chains/ton.en-US.mdx
- src/pages/developers/standards/overview.zh-CN.mdx
- src/pages/developers/evm/cctx.zh-CN.mdx
- src/pages/developers/protocol/ton.en-US.md
- src/pages/developers/chains/_meta.zh-CN.json
- src/pages/developers/protocol/evm.zh-CN.md
- src/pages/developers/protocol/_meta.en-US.json
- src/pages/developers/chains/bitcoin.en-US.mdx
- src/pages/developers/tutorials/solana.en-US.mdx
- src/pages/developers/architecture/observers.zh-CN.mdx
- src/pages/developers/protocol/sui.en-US.md
- src/pages/developers/chains/sui.zh-CN.mdx
- src/pages/developers/evm/gas.en-US.mdx
- src/pages/reference/toolkit.zh-CN.mdx
- src/pages/developers/standards/overview.en-US.mdx
- src/pages/developers/architecture/whitelisting.zh-CN.mdx
- src/pages/developers/standards/_meta.zh-CN.json
- src/pages/developers/standards/_meta.en-US.json
- src/pages/developers/chains/zetachain.en-US.mdx
- src/pages/developers/evm/gateway.zh-CN.mdx
- src/pages/developers/architecture/_meta.zh-CN.json
- src/pages/reference/localnet.zh-CN.mdx
- src/pages/developers/evm/index.zh-CN.mdx
- src/pages/developers/tutorials/swap.en-US.mdx
- src/pages/developers/standards/nft.en-US.mdx
- src/pages/developers/evm/zrc20.en-US.mdx
- src/pages/developers/tutorials/frontend.en-US.mdx
- src/pages/developers/tutorials/sui-withdraw-and-call.en-US.mdx
- src/pages/reference/mcp.zh-CN.mdx
- src/pages/developers/protocol/sui.zh-CN.md
- src/pages/developers/protocol/ton.zh-CN.md
- src/pages/developers/evm/cctx.en-US.mdx
- src/pages/developers/tutorials/messaging.en-US.mdx
- src/pages/developers/evm/throughput.en-US.mdx
- src/pages/developers/tutorials/sui-withdraw-and-call.zh-CN.mdx
- src/pages/developers/tutorials/solana.zh-CN.mdx
- src/pages/developers/chains/list.en-US.mdx
- src/pages/developers/evm/throughput.zh-CN.mdx
- src/pages/developers/standards/token.zh-CN.mdx
- src/pages/developers/protocol/_meta.zh-CN.json
- src/pages/developers/tutorials/_meta.zh-CN.json
- src/pages/developers/tutorials/call.en-US.mdx
- src/pages/developers/chains/evm.en-US.mdx
- src/pages/developers/chains/ton.zh-CN.mdx
- src/pages/developers/tutorials/intro.en-US.mdx
- src/pages/developers/chains/sui.en-US.mdx
- src/pages/developers/tutorials/hello.en-US.mdx
- src/pages/developers/tutorials/sui.en-US.mdx
- src/pages/reference/registry.en-US.mdx
- src/pages/developers/tutorials/intro.zh-CN.mdx
- src/pages/developers/chains/functionality.en-US.mdx
- src/pages/reference/_meta.zh-CN.json
- src/pages/developers/standards/token.en-US.mdx
- src/pages/developers/chains/evm.zh-CN.mdx
- src/pages/developers/standards/nft.zh-CN.mdx
- src/pages/developers/tutorials/swap.zh-CN.mdx
- src/pages/developers/chains/zetachain.zh-CN.mdx
- src/pages/developers/protocol/solana.en-US.md
- src/pages/developers/evm/zrc20.zh-CN.mdx
- src/pages/reference/registry.zh-CN.mdx
- src/pages/developers/chains/functionality.zh-CN.mdx
- src/pages/developers/architecture/whitelisting.en-US.mdx
- src/pages/developers/chains/solana.zh-CN.mdx
- src/pages/developers/protocol/solana.zh-CN.md
- src/pages/developers/chains/list.zh-CN.mdx
- src/pages/reference/toolkit.en-US.mdx
- src/pages/developers/tutorials/hello.zh-CN.mdx
- src/pages/developers/tutorials/frontend.zh-CN.mdx
- src/pages/reference/cli.en-US.mdx
- src/pages/developers/tutorials/messaging.zh-CN.mdx
- src/pages/developers/architecture/observers.en-US.mdx
- src/pages/developers/tutorials/call.zh-CN.mdx
- src/pages/developers/chains/bitcoin.zh-CN.mdx
- src/pages/reference/cli.zh-CN.mdx
- src/pages/developers/evm/gas.zh-CN.mdx
- src/pages/developers/chains/solana.en-US.mdx
- src/pages/developers/tutorials/sui.zh-CN.mdx
Comment on lines
+9
to
+11
| [Cosmos SDK](https://docs.cosmos.network/) and uses the | ||
| [CometBFT](https://docs.cometbft.com/) consensus engine, with full EVM | ||
| compatibility provided by [Cosmos EVM](https://evm.cosmos.network/). |
Contributor
There was a problem hiding this comment.
Use canonical www.zetachain.com URLs for all hardcoded links.
Hardcoded links in this page currently use non-canonical domains and relative paths. Please update them to canonical https://www.zetachain.com/... URLs per policy.
As per coding guidelines, "All hardcoded URLs in MDX content must use the canonical domain www.zetachain.com."
Also applies to: 19-23
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/about/overview.en-US.mdx` around lines 9 - 11, Update the hardcoded
links in the MDX content so they use the canonical domain
https://www.zetachain.com; specifically replace the URLs for the link texts
"Cosmos SDK", "CometBFT", and "Cosmos EVM" (and any other hardcoded links in the
same file mentioned in the comment) with their canonical
https://www.zetachain.com/... counterparts, ensuring each href begins with
https://www.zetachain.com/ and preserving the visible link text and path
segments.
| <RoadmapPillars /> | ||
| <CurrentPageNavigationSections /> | ||
| </div> | ||
| The chain has ~5 second blocks with instant finality, an EIP-1559 fee market, |
Contributor
There was a problem hiding this comment.
Hyphenate compound modifier in Line 13.
Use ~5-second blocks instead of ~5 second blocks for correct grammar.
🧰 Tools
🪛 LanguageTool
[grammar] ~13-~13: Use a hyphen to join words.
Context: .../evm.cosmos.network/). The chain has ~5 second blocks with instant finality, an ...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/about/overview.en-US.mdx` at line 13, Replace the unhyphenated
compound modifier "~5 second blocks" with the hyphenated form "~5-second blocks"
in the text (look for the phrase "~5 second blocks" in the content, e.g., in the
sentence beginning "The chain has ~5 second blocks...") so the modifier is
grammatically correct.
Comment on lines
+9
to
+11
| [Cosmos SDK](https://docs.cosmos.network/) and uses the | ||
| [CometBFT](https://docs.cometbft.com/) consensus engine, with full EVM | ||
| compatibility provided by [Cosmos EVM](https://evm.cosmos.network/). |
Contributor
There was a problem hiding this comment.
Apply canonical www.zetachain.com URLs in this MDX page.
Hardcoded links here do not follow the canonical-domain rule. Please switch them to https://www.zetachain.com/... URLs.
As per coding guidelines, "All hardcoded URLs in MDX content must use the canonical domain www.zetachain.com."
Also applies to: 19-23
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/about/overview.zh-CN.mdx` around lines 9 - 11, Replace all
hardcoded external links in the MDX page with the canonical www.zetachain.com
domain: change the occurrences of https://docs.cosmos.network/,
https://docs.cometbft.com/, and https://evm.cosmos.network/ (found around the
block showing Cosmos SDK / CometBFT / Cosmos EVM and additionally in the section
referenced at lines 19-23) to their corresponding https://www.zetachain.com/...
canonical URLs; ensure every hardcoded URL in src/pages/about/overview.zh-CN.mdx
uses https://www.zetachain.com as the base and update any remaining links
elsewhere in that file to follow the same rule so no MDX links point to
non-canonical domains.
Comment on lines
+2
to
+3
| title: Smart Contracts | ||
| description: Deploy and interact with EVM smart contracts on ZetaChain. |
Contributor
There was a problem hiding this comment.
Restore Chinese-localized content for the zh-CN page.
This locale page is entirely English now, which is an i18n regression for Chinese users and breaks locale expectations in production docs. Please provide Chinese frontmatter and body copy for this file.
Also applies to: 6-16
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/start/app.zh-CN.mdx` around lines 2 - 3, The zh-CN locale page has
English frontmatter and content; restore Chinese localization by replacing the
frontmatter fields (title, description) with Chinese equivalents and translating
the MDX body into Chinese; update the frontmatter keys in app.zh-CN.mdx (title,
description) to Chinese strings like "智能合约" and a Chinese description, and
translate all English body headings, paragraphs and code comments into
Simplified Chinese to match the locale; apply the same fix pattern to the other
affected locale files referenced (lines 6-16) to ensure consistency across zh-CN
pages.
Comment on lines
+2
to
+3
| title: Build on ZetaChain | ||
| description: Deploy EVM smart contracts on ZetaChain using Hardhat, Foundry, or any standard EVM toolchain. |
Contributor
There was a problem hiding this comment.
Localize the zh-CN build page instead of shipping English copy.
The .zh-CN.mdx page currently contains English frontmatter and body content, which degrades the localized docs experience and should be corrected before release.
Also applies to: 6-18
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/start/build.zh-CN.mdx` around lines 2 - 3, The zh-CN localized page
has English frontmatter fields "title" and "description" and English body copy;
replace those with Chinese translations and localize the entire MDX body
(including headings, paragraphs, code comments and any UI strings). Update the
"title" and "description" frontmatter to Chinese equivalents, and scan the rest
of the document for remaining English (lines noted around the top and also lines
6-18) to translate them into Simplified Chinese so the page is fully localized.
…atibility - Created open-next.config.ts to define Cloudflare configuration. - Added patch-cloudflare-deps.mjs script to strip incompatible export conditions from @emotion packages. - Introduced wrangler.jsonc for Cloudflare Workers configuration, specifying assets and compatibility settings.
Contributor
|
❌ Cloudflare Workers Preview — Deploy failed. |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/deploy.yml:
- Around line 158-162: The cleanup-preview job currently runs npx wrangler
delete (using WORKER_NAME="zetachain-docs-pr-${{
github.event.pull_request.number }}") without reproducing the same pinned
toolchain as deploy/deploy-preview; update the cleanup-preview job to mirror the
other jobs by adding actions/checkout, actions/setup-node with the repo Node
version, and a yarn install --frozen-lockfile step, then replace npx wrangler
delete with the pinned invocation (yarn wrangler delete --name "$WORKER_NAME"
--force) so the same Wrangler version is used for worker deletion.
In `@next.config.js`:
- Around line 9-11: The dynamic import promise for `@opennextjs/cloudflare`
currently swallows errors in the .catch(() => {}) handler; update the catch to
surface the failure by logging the error (e.g., console.warn or a logger) and
include the thrown error details and context (mentioning
initOpenNextCloudflareForDev) so local Cloudflare dev-init failures aren't
silent—replace the empty catch with a handler that logs a descriptive warning
plus the error object.
In `@package.json`:
- Line 9: Update the Next.js dependency to a supported release (e.g., set "next"
to at least 15.5.15 or 16.2.6+) in package.json and remove the
--dangerouslyUseUnsupportedNextVersion flag from the "build:cloudflare" npm
script so the script "build:cloudflare" becomes safe to run with
`@opennextjs/cloudflare` v1.17.1; after changing the "next" version, run install
and validate the build to ensure compatibility with any breaking changes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 61740c3c-a06b-4a15-8746-4f1da24de6d5
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (62)
.github/workflows/deploy.yml.gitignoreapp/api/chat/route.tsnext.config.jsopen-next.config.tspackage.jsonscripts/patch-cloudflare-deps.mjssrc/components/Home/Home.constants.tsxsrc/components/Home/Home.graphql.contentful.tssrc/components/Home/components/EcosystemCarousel/EcosystemCarousel.tsxsrc/components/Home/components/EcosystemCarousel/Slide.tsxsrc/components/Home/components/EcosystemCarousel/SlideItemsIndicator.tsxsrc/components/Home/components/EngineeringBlog.tsxsrc/components/Home/components/HomePage.tsxsrc/components/Home/components/JoinCommunity.tsxsrc/components/Home/components/VideosSection.tsxsrc/components/Home/components/svg/EngineeringBlog.tsxsrc/components/Home/components/svg/JoinCommunitySvgs.tsxsrc/components/Home/hooks/useHomePageContent.tssrc/components/Home/index.tssrc/components/shared/components/Layout/Layout.constants.tsxsrc/pages/_meta.en-US.jsonsrc/pages/_meta.zh-CN.jsonsrc/pages/developers/_meta.en-US.jsonsrc/pages/developers/_meta.zh-CN.jsonsrc/pages/developers/addresses.en-US.mdxsrc/pages/developers/addresses.zh-CN.mdxsrc/pages/developers/architecture/_meta.en-US.jsonsrc/pages/developers/architecture/_meta.zh-CN.jsonsrc/pages/developers/architecture/modules.en-US.mdxsrc/pages/developers/architecture/modules.zh-CN.mdxsrc/pages/developers/architecture/overview.en-US.mdxsrc/pages/developers/architecture/overview.zh-CN.mdxsrc/pages/developers/architecture/privileged.en-US.mdxsrc/pages/developers/architecture/privileged.zh-CN.mdxsrc/pages/developers/erc20.en-US.mdxsrc/pages/developers/erc20.zh-CN.mdxsrc/pages/developers/evm.en-US.mdxsrc/pages/developers/evm.zh-CN.mdxsrc/pages/developers/evm/_meta.en-US.jsonsrc/pages/developers/evm/_meta.zh-CN.jsonsrc/pages/developers/evm/evm.en-US.mdxsrc/pages/developers/evm/evm.zh-CN.mdxsrc/pages/developers/overview.en-US.mdxsrc/pages/developers/overview.zh-CN.mdxsrc/pages/developers/rewards.en-US.mdxsrc/pages/developers/rewards.zh-CN.mdxsrc/pages/developers/tutorials/_meta.en-US.jsonsrc/pages/developers/tutorials/_meta.zh-CN.jsonsrc/pages/developers/tutorials/staking.en-US.mdxsrc/pages/developers/tutorials/staking.zh-CN.mdxsrc/pages/developers/zeta.en-US.mdxsrc/pages/developers/zeta.zh-CN.mdxsrc/pages/developers/zetacored.en-US.mdsrc/pages/developers/zetacored.zh-CN.mdsrc/pages/reference/tools/address-converter.en-US.mdxsrc/pages/reference/tools/address-converter.zh-CN.mdxsrc/pages/start/app.en-US.mdxsrc/pages/start/app.zh-CN.mdxsrc/pages/start/build.en-US.mdxsrc/pages/start/build.zh-CN.mdxwrangler.jsonc
💤 Files with no reviewable changes (28)
- src/components/Home/components/svg/JoinCommunitySvgs.tsx
- src/pages/developers/evm/evm.en-US.mdx
- src/pages/developers/architecture/modules.en-US.mdx
- src/pages/developers/evm/evm.zh-CN.mdx
- src/pages/developers/tutorials/staking.zh-CN.mdx
- src/components/Home/components/svg/EngineeringBlog.tsx
- src/pages/developers/architecture/_meta.zh-CN.json
- src/components/Home/components/JoinCommunity.tsx
- src/pages/developers/tutorials/staking.en-US.mdx
- src/components/Home/components/EngineeringBlog.tsx
- app/api/chat/route.ts
- src/components/Home/components/VideosSection.tsx
- src/pages/developers/architecture/overview.en-US.mdx
- src/pages/developers/architecture/modules.zh-CN.mdx
- src/pages/developers/architecture/privileged.zh-CN.mdx
- src/pages/developers/tutorials/_meta.en-US.json
- src/components/Home/index.ts
- src/components/Home/components/EcosystemCarousel/SlideItemsIndicator.tsx
- src/pages/developers/tutorials/_meta.zh-CN.json
- src/components/Home/Home.constants.tsx
- src/pages/developers/architecture/overview.zh-CN.mdx
- src/pages/developers/architecture/privileged.en-US.mdx
- src/components/Home/components/EcosystemCarousel/EcosystemCarousel.tsx
- src/components/Home/components/EcosystemCarousel/Slide.tsx
- src/pages/developers/evm/_meta.zh-CN.json
- src/components/Home/Home.graphql.contentful.ts
- src/pages/developers/evm/_meta.en-US.json
- src/pages/developers/architecture/_meta.en-US.json
✅ Files skipped from review due to trivial changes (9)
- .gitignore
- src/pages/_meta.zh-CN.json
- src/pages/developers/overview.en-US.mdx
- src/pages/_meta.en-US.json
- src/pages/developers/evm.zh-CN.mdx
- src/pages/developers/overview.zh-CN.mdx
- src/pages/developers/_meta.en-US.json
- src/components/shared/components/Layout/Layout.constants.tsx
- src/pages/developers/evm.en-US.mdx
Comment on lines
+158
to
+162
| - name: Delete preview worker | ||
| run: | | ||
| WORKER_NAME="zetachain-docs-pr-${{ github.event.pull_request.number }}" | ||
| npx wrangler delete --name "$WORKER_NAME" --force | ||
| env: |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's check if the deploy.yml file exists and read it
git ls-files '.github/workflows/deploy.yml'Repository: zeta-chain/docs
Length of output: 88
🏁 Script executed:
# Read the deploy.yml file to examine the cleanup-preview job and others
cat -n .github/workflows/deploy.ymlRepository: zeta-chain/docs
Length of output: 8105
Align cleanup-preview job with pinned Wrangler version used in other jobs.
The cleanup-preview job uses npx wrangler delete without setting up dependencies, while the deploy and deploy-preview jobs establish a controlled environment with yarn install --frozen-lockfile and invoke yarn wrangler. This inconsistency means the cleanup command may resolve a different Wrangler version, potentially causing worker deletion to fail. Add checkout, Node setup, and yarn install steps to ensure consistent tooling across all jobs.
Suggested fix
cleanup-preview:
if: github.event_name == 'pull_request' && github.event.action == 'closed'
runs-on: ubuntu-latest
steps:
+ - uses: actions/checkout@v4
+ - uses: actions/setup-node@v4
+ with:
+ node-version: 20
+ cache: yarn
+ - run: yarn install --frozen-lockfile
- name: Delete preview worker
run: |
WORKER_NAME="zetachain-docs-pr-${{ github.event.pull_request.number }}"
- npx wrangler delete --name "$WORKER_NAME" --force
+ yarn wrangler delete --name "$WORKER_NAME" --force🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/deploy.yml around lines 158 - 162, The cleanup-preview job
currently runs npx wrangler delete (using WORKER_NAME="zetachain-docs-pr-${{
github.event.pull_request.number }}") without reproducing the same pinned
toolchain as deploy/deploy-preview; update the cleanup-preview job to mirror the
other jobs by adding actions/checkout, actions/setup-node with the repo Node
version, and a yarn install --frozen-lockfile step, then replace npx wrangler
delete with the pinned invocation (yarn wrangler delete --name "$WORKER_NAME"
--force) so the same Wrangler version is used for worker deletion.
Comment on lines
+9
to
+11
| import("@opennextjs/cloudflare") | ||
| .then(({ initOpenNextCloudflareForDev }) => initOpenNextCloudflareForDev()) | ||
| .catch(() => {}); |
Contributor
There was a problem hiding this comment.
Avoid swallowing Cloudflare dev-init failures silently.
On Line 11, the empty catch suppresses actionable errors and makes local binding issues opaque. At least log a warning.
Suggested fix
if (process.env.NODE_ENV !== "production") {
import("`@opennextjs/cloudflare`")
.then(({ initOpenNextCloudflareForDev }) => initOpenNextCloudflareForDev())
- .catch(() => {});
+ .catch((error) => {
+ // Keep dev boot resilient, but make failures visible.
+ // eslint-disable-next-line no-console
+ console.warn("Cloudflare dev bindings init failed:", error);
+ });
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| import("@opennextjs/cloudflare") | |
| .then(({ initOpenNextCloudflareForDev }) => initOpenNextCloudflareForDev()) | |
| .catch(() => {}); | |
| import("`@opennextjs/cloudflare`") | |
| .then(({ initOpenNextCloudflareForDev }) => initOpenNextCloudflareForDev()) | |
| .catch((error) => { | |
| // Keep dev boot resilient, but make failures visible. | |
| // eslint-disable-next-line no-console | |
| console.warn("Cloudflare dev bindings init failed:", error); | |
| }); |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@next.config.js` around lines 9 - 11, The dynamic import promise for
`@opennextjs/cloudflare` currently swallows errors in the .catch(() => {})
handler; update the catch to surface the failure by logging the error (e.g.,
console.warn or a logger) and include the thrown error details and context
(mentioning initOpenNextCloudflareForDev) so local Cloudflare dev-init failures
aren't silent—replace the empty catch with a handler that logs a descriptive
warning plus the error object.
| "scripts": { | ||
| "build": "NODE_OPTIONS=--max-old-space-size=6144 yarn clean && yarn graphql-codegen && next build", | ||
| "postbuild": "next-sitemap", | ||
| "build:cloudflare": "yarn build && node scripts/patch-cloudflare-deps.mjs && opennextjs-cloudflare build --dangerouslyUseUnsupportedNextVersion", |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
For @opennextjs/cloudflare v1.17.1, what Next.js versions are officially supported? Is next@14.2.33 supported without --dangerouslyUseUnsupportedNextVersion?
💡 Result:
For @opennextjs/cloudflare v1.17.1, the officially supported Next.js versions are Next.js 14, 15, and 16 [1]. Specifically, the adapter supports the latest minor and patch versions of these major releases [1]. Regarding your question about next@14.2.33: Yes, it is supported without needing the --dangerouslyUseUnsupportedNextVersion flag. The adapter's version check logic requires Next.js 14.2 or greater [2], and next@14.2.33 falls well within the supported range for the 14.x line [1]. As of May 2026, the peer dependency requirements for @opennextjs/cloudflare have been refined to ensure compatibility with stable releases, specifically requiring next >=15.5.15 <16 || >=16.2.6 [3][4]. While Next.js 14 is supported, it is noted that official support for Next.js 14 by the Next.js team has ended [1].
Citations:
- 1: https://opennext.js.org/cloudflare
- 2: opennextjs/opennextjs-cloudflare@ae3d43d
- 3: https://www.npmjs.com/package/@opennextjs/cloudflare
- 4: https://registry.npmjs.org/@opennextjs/cloudflare
🏁 Script executed:
cat package.json | head -30Repository: zeta-chain/docs
Length of output: 1650
🏁 Script executed:
cat package.json | grep -A 5 -E '"(next|`@opennextjs/cloudflare`)"'Repository: zeta-chain/docs
Length of output: 471
Upgrade Next.js to a version within the officially supported range for @opennextjs/cloudflare v1.17.1 and remove the --dangerouslyUseUnsupportedNextVersion flag.
The repository uses next@14.2.33, which falls outside the currently supported peer dependency range for @opennextjs/cloudflare (next >=15.5.15 <16 || >=16.2.6 as of May 2026). The --dangerouslyUseUnsupportedNextVersion flag on line 9 serves as a workaround for this version mismatch, introducing unnecessary deployment risk. Upgrade Next.js to version 15.5.15 or later (or 16.2.6+ for the 16.x line) and remove the flag from the build pipeline.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 9, Update the Next.js dependency to a supported release
(e.g., set "next" to at least 15.5.15 or 16.2.6+) in package.json and remove the
--dangerouslyUseUnsupportedNextVersion flag from the "build:cloudflare" npm
script so the script "build:cloudflare" becomes safe to run with
`@opennextjs/cloudflare` v1.17.1; after changing the "next" version, run install
and validate the build to ensure compatibility with any breaking changes.
…are compatibility" This reverts commit 1d1dd96.
Move details, api, and openapi pages from reference/network/ up to reference/ so they appear directly under the Tools section. Delete the contract addresses page along with its now-orphaned ContractAddresses component. Update all cross-references and the maintained llms.txt / llms-full.txt entries.
… with external links
- Updated Home.constants.tsx to modify SHIP_FASTER_CARD_LINKS with new links and descriptions. - Refactored BuildForNow component to enhance messaging and replace chain SVGs with model SVGs. - Removed Ecosystem component from HomePage and its associated loading logic. - Adjusted NarrowCardLinkContent to ensure SVGs scale correctly. - Updated ShipFaster component to reflect new branding and messaging for ZetaChain. - Created new ModelSvgs.tsx file to house SVGs for various AI models. - Added ZetaChainSvg to ShipFasterSvgs.tsx for branding consistency. - Modified gradient definitions in FadeRightSvg for improved visual consistency.
… wallet documentation for clarity
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Medium Risk
This removes a large set of developer documentation pages and nav metadata, which may break existing internal links/routes (e.g., chain gateway docs) if redirects or references aren’t updated. Content-only changes otherwise, but the scope of deletions makes docs navigation regressions more likely.
Overview
Reworks the About overview pages to use short static Markdown copy (network description + Explore links) instead of rendering the previous component-based sections, and updates frontmatter title/description.
Significantly prunes the Developers docs IA/content by simplifying
_metanavigation (renaming/condensing sections likeUniversal EVM→EVM) and deleting multiple pages/sections, includingdevelopers/chains/*gateway/how-to content, severaldevelopers/evm/*reference pages,developers/protocol/*metadata, and somedevelopers/architecture/*topics (e.g., observers, ERC-20 whitelisting).Reviewed by Cursor Bugbot for commit d3bc116. Configure here.
Summary by CodeRabbit
Documentation Updates
Homepage Changes
Navigation Updates
New/Localized Content