chore: replace some redirects to old-docs.ton.org with existing pages

[novusnota]

Closes #2177

Summary by CodeRabbit

• Documentation
  • Improved security warning formatting in the style guide using enhanced callout components.
  • Updated legacy documentation redirects to new in-site routes.
  • Enhanced jetton security guidance with recommendations for name verification.
  • Updated wallet implementation reference links and documentation links.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify-ton-docs	🟢 Ready	View Preview	May 18, 2026, 11:56 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR migrates documentation away from old-docs.ton.org by updating MDX pages to use improved callout components and reconfiguring redirect rules in docs.json. Content pages convert blockquote warnings to structured Aside components, and legacy redirect destinations are updated to point to new internal documentation routes.

Changes

Documentation Migration: Aside Components and Legacy Redirect Updates

Layer / File(s)	Summary
MDX Aside Component Migration contribute/style-guide.mdx, standard/tokens/jettons/comparison.mdx, standard/wallets/v4.mdx	Three MDX pages import and use the Aside component for improved callout rendering. The contribute/style-guide page converts a "funds at risk" blockquote into a structured caution with testnet transfer example. The jettons/comparison page adds a security caution about jetton name verification. The wallet V4 page adds upstream repository links and standardizes TON Connect capitalization.
Legacy Redirect Target Updates docs.json	Eight redirect entries in docs.json are updated to replace stale old-docs.ton.org destinations with new internal documentation routes. Updated paths include /v3/documentation/dapps/assets/usdt, /v3/documentation/dapps/defi/subscriptions, /v3/guidelines/dapps/asset-processing/compressed-nfts, /v3/guidelines/nodes/running-nodes/staking-with-nominator-pools, and multiple /v3/contribute/* paths, all now pointing to appropriate in-site locations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• ton-org/docs#2089: Both PRs modify docs.json's redirects configuration by updating destination URLs for legacy documentation paths.

Suggested labels

3p

Suggested reviewers

• delovoyhomie
• thekiba

Poem

🐰 A rabbit hops through old docs, finding paths,
Migrating warnings into callout baths,
The Asides glow with caution bright,
While redirects leap to new light—
Old-docs.ton.org fades from sight! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The PR includes out-of-scope changes: updates to style-guide.mdx, comparison.mdx, and v4.mdx files that are unrelated to replacing old-docs.ton.org redirects.	Remove documentation content changes (Aside components, rewording, and link updates) that are not part of the redirect replacement objective in issue #2177.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main objective: replacing redirects pointing to old-docs.ton.org with links to existing documentation pages.
Linked Issues check	✅ Passed	The PR successfully addresses issue #2177 by updating redirects in docs.json from old-docs.ton.org destinations to new in-site documentation routes across multiple pages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch closes-2177/best-viewed-by-netscape-navigator-4.0

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

standard/tokens/jettons/comparison.mdx (1)

42-48: ⚡ Quick win

Consider adding a title to improve scannability.

The Aside component in the style guide example (contribute/style-guide.mdx lines 80-82) includes a title prop for improved scannability. Adding a descriptive title here (e.g., title="Verify jetton authenticity" or title="Security warning") would help readers quickly identify the warning type when scanning the page.

♻️ Suggested enhancement

 <Aside
   type="caution"
+  title="Verify jetton authenticity"
 >
   On TON, multiple jettons can share the same name — a counterfeit jetton may look identical to the real USDT but have no value. Verify legitimacy by confirming [USDT's jetton master address](https://tonviewer.com/EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs?section=jetton).

As per coding guidelines, "Keep it scannable. Use short sections and paragraphs, clear headings, lists, and tables. Most readers skim to find the next action."

🤖 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 `@standard/tokens/jettons/comparison.mdx` around lines 42 - 48, The Aside
component used for the caution block lacks a title prop which harms
scannability; update the Aside instance (the Aside component around the jetton
warning) to include a descriptive title such as title="Verify jetton
authenticity" or title="Security warning" so readers can immediately identify
the note type when scanning the page, ensuring the prop is added to the same
Aside element and matches styling conventions used elsewhere in the style guide
examples.

🤖 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.

Nitpick comments:
In `@standard/tokens/jettons/comparison.mdx`:
- Around line 42-48: The Aside component used for the caution block lacks a
title prop which harms scannability; update the Aside instance (the Aside
component around the jetton warning) to include a descriptive title such as
title="Verify jetton authenticity" or title="Security warning" so readers can
immediately identify the note type when scanning the page, ensuring the prop is
added to the same Aside element and matches styling conventions used elsewhere
in the style guide examples.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e27a9abb-5628-416e-839d-c526edd9fa60

📥 Commits

Reviewing files that changed from the base of the PR and between 7951a09 and b22f980.

📒 Files selected for processing (4)

• contribute/style-guide.mdx
• docs.json
• standard/tokens/jettons/comparison.mdx
• standard/wallets/v4.mdx