Nextra 2 (Next.js) documentation site. Locales: en-US (default), zh-CN.
src/pages/— MDX content pages, organized by sectionsrc/pages/*/_meta.en-US.json/_meta.zh-CN.json— Nextra sidebar config with titles and descriptionssrc/components/— React components used in MDX pagessrc/config/next-seo.config.ts— Global SEO defaults (title, description, OG tags)src/theme.config.tsx— Nextra theme config (head tags, canonical URL, i18n)next-sitemap.config.js— Sitemap generation configpublic/robots.txt— Auto-generated by next-sitemap
Every content change MUST follow these rules to maintain search engine and AI search visibility.
All URLs must use www.zetachain.com. Never use bare zetachain.com. Check:
src/constants/globalLinks.tssrc/config/next-seo.config.ts- Any hardcoded URLs in MDX content
Every new .mdx page must have:
- Frontmatter with
titleanddescription:--- title: "Page Title" description: "One-sentence factual summary of the page content" ---
_meta.en-US.jsonentry as an object withtitleanddescription(not a bare string):{ "page-slug": { "title": "Page Title", "description": "Short description for SEO" } }- Both locales — every
*.en-US.mdxneeds a corresponding*.zh-CN.mdx, and every_meta.en-US.jsonneeds a_meta.zh-CN.json.
- All
<Image>and<img>tags must have descriptivealttext (not file paths). - Decorative images use
alt="".
- Use
rel="noopener noreferrer"ontarget="_blank"links. - Never use
rel="nofollow"for links to partner/ecosystem sites (it tells search engines to ignore the link).
When adding third-party services or partners to the docs, add them to:
src/pages/about/services/index.en-US.mdx(and zh-CN) — the services table- Optionally a dedicated subpage under
src/pages/about/services/with_metaentries
- Each page should have exactly one
<h1>(provided by the Hero component via frontmatter title). - Content headings in MDX should start at
##(h2), not#(h1).
yarn dev # Dev server on port 3001
yarn build # Production build
yarn typecheck # TypeScript check
yarn lint # ESLint