[docs-agent] Add Cronos quickstart + FAQ pages#1442
Merged
Conversation
Daikon's Update Specs workflow generated `content/api-reference/cronos/cronos-api-overview.mdx` and the chains-tab section for Cronos EVM after chain-config PR #6398 flipped availability to PUBLIC, but the quickstart and FAQ pages weren't part of that generation and need manual scaffolding. Adds: - `content/api-reference/cronos/cronos-api-quickstart.mdx`: viem-based quickstart (client setup, latest block, address balance, block data, tx by hash, tx receipt). Pattern-matched from ApeChain / CrossFi / Katana. Uses `cronos` chain export from `viem/chains` and the `cronos-mainnet.g.alchemy.com/v2/YOUR_ALCHEMY_API_KEY` endpoint. - `content/api-reference/cronos/cronos-api-faq.mdx`: standard EVM-chain FAQ (what is it, API surface, EVM compatibility, libraries, languages, gas token `$CRO`, methods list, support). Pattern-matched from ApeChain and Katana. - `content/docs.yml`: adds Quickstart at the top and FAQ at the bottom of the existing Cronos section (matching the Katana / Kaia / other-chain layout). Refs DOCS-136 Requested-by: @dslovinsky
🔗 Preview Mode
|
SahilAujla
approved these changes
Jul 10, 2026
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
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.
Summary
Adds the Cronos quickstart and FAQ pages that Daikon's Update Specs workflow didn't generate. Daikon created
cronos-api-overview.mdxand the chains-tab section after chain-config PR #6398 flippedavailability: PRERELEASE→PUBLIC, but quickstart and FAQ pages need manual scaffolding.Changes
content/api-reference/cronos/cronos-api-quickstart.mdx: viem-based quickstart (client setup, latest block, address balance, block data, tx by hash, tx receipt). Pattern-matched from ApeChain / CrossFi / Katana. Uses thecronoschain export fromviem/chainsand thecronos-mainnet.g.alchemy.com/v2/YOUR_ALCHEMY_API_KEYendpoint (live-verified,eth_chainIdreturns0x19).content/api-reference/cronos/cronos-api-faq.mdx: standard EVM-chain FAQ (what is it, API surface, EVM compatibility, libraries, languages, gas token$CRO, methods list, support). Pattern-matched from ApeChain and Katana.content/docs.yml: adds Quickstart at the top and FAQ at the bottom of the existing Cronos section (matching the Katana / Kaia / other-chain layout).The Cronos section's placement in
docs.yml(line ~1261, at the end of the chains tab rather than alphabetically between Clankermon and CrossFi) is a Daikon-side ordering quirk shared with the Kaia section. Flagged for a separate ticket; not fixed here to keep PR scope tight and avoid churn on the next Daikon run.Linear
DOCS-136
Requested by
@dslovinsky (via Slack thread)