docs: remove Advanced section from Advanced tab

[devin-ai-integration]

Description

Removes the "Advanced" group from the Advanced tab in the docs navigation, along with all associated files and cross-references. The Security section has been preserved and relocated as its own top-level group below Guides.

Deleted content (33 files):

• advanced/api/ — Core (Pairing, Relay, Shared Core) and Sign API docs
• advanced/multichain/ — All RPC reference pages (19 chains) and Polkadot integration guides
• advanced/providers/ — Ethereum, Universal, and Solana adapter provider docs
• advanced/walletkit-migration.mdx

Relocated:

• advanced/security/ (Security Information, Content Security Policy) — moved from within the "Advanced" group to a new standalone Security group below Guides

Updated references in remaining files:

• Removed broken links to deleted RPC reference and Polkadot guide pages in supported-chains.mdx, bitcoin.mdx, usage.mdx (iOS), universal-connector.mdx, and several snippets
• Removed the now-invalid /advanced/rpc-reference/:path* redirect from docs.json

Not deleted (intentionally preserved):

• advanced/faq.mdx — still referenced in the Technical Reference group
• advanced/security/ — preserved and promoted to its own navigation group
• advanced/glossary.mdx and advanced/walletconnectmodal/ — not part of the removed "Advanced" group
• cloud/ pages (chains, wallets, explorer, relay) — shared across other tabs

New Advanced tab structure: Migration → Guides → Security → Technical Reference

Human review checklist

• Verify docs.json navigation structure renders correctly (Migration → Guides → Security → Technical Reference)
• Confirm no remaining pages have broken links to removed advanced/ content (grep for /advanced/multichain, /advanced/api, /advanced/providers)
• Consider whether orphaned files (advanced/glossary.mdx, advanced/walletconnectmodal/) should also be cleaned up

Tests

• Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
• Ran a grammar check on the updated/created content using ChatGPT.

Direct link to the deployed preview files

• Advanced Tab (post-removal)
• Security Section

---

Link to Devin run | Requested by: TomTom

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

Claude finished @devin-ai-integration[bot]'s task in 40s —— View job

---

PR Review

• Read tone of voice guidance
• Analyze docs.json changes
• Check modified MDX files for broken links/issues
• Run breaking changes analysis
• Run data classification analysis
• Post final review

---

Breaking changes: None. Docs-only removals with no API/code contracts affected.

Remaining broken references to deleted content: None found in .mdx or .json files.

Navigation structure (Advanced tab): Valid — Migration → Guides → Technical Reference remain intact.

Found 4 issue(s)

Issue 1: Stale ignorePaths entries in .cspell.json referencing deleted files

ID: cspell-stale-ignore-paths-a3f1
File: .cspell.json:5-8
Severity: LOW
Category: code_quality

Context:

• Pattern: .cspell.json ignorePaths still lists paths under docs/advanced/multichain/polkadot/ and docs/advanced/multichain/rpc-reference/ that were deleted by this PR.
• Risk: Stale ignore entries accumulate technical debt and mislead future contributors about which files need spell-check exemptions.
• Impact: No functional impact; cspell silently skips missing paths.

Recommendation: Remove the stale entries from .cspell.json ignorePaths:

"docs/advanced/multichain/polkadot/dapp-integration-guide.md",
"docs/advanced/multichain/polkadot/wallet-integration-guide.md",
"docs/advanced/multichain/rpc-reference/bitcoin-rpc.md",
"docs/advanced/multichain/rpc-reference/dogecoin-rpc.md",
"docs/advanced/multichain/rpc-reference/everscale-rpc.md",
"docs/advanced/multichain/rpc-reference/litecoin-rpc.md"

Fix this →

---

Issue 2: Orphaned files not in navigation and not linked from anywhere

ID: advanced-orphaned-files-nav-b8d2
File: advanced/glossary.mdx, advanced/walletconnectmodal/about.mdx (+ options.mdx, theming.mdx)
Severity: MEDIUM
Category: code_quality

Context:

• Pattern: advanced/glossary.mdx and advanced/walletconnectmodal/ (3 files) exist on disk but are absent from docs.json navigation and have no inbound links from any .mdx file.
• Risk: Pages accessible by direct URL but invisible in nav and unreachable through normal browsing; will receive no maintenance.
• Impact: SEO noise, stale content accumulation, and confusion for contributors.

Recommendation: Either add to docs.json navigation if still relevant, or delete (with redirects if the URLs have external inbound links). The PR description notes these as "intentionally preserved" — the decision should be explicit before merge.

---

Issue 3: Hardcoded demo project ID in documentation snippets (pre-existing)

ID: dcl-universal-connector-hardcoded-projectid-a3f2
File: appkit/recipes/universal-connector.mdx:69, snippets/appkit/react/core/about/implementation.mdx:13, snippets/appkit/javascript/core/about/implementation.mdx:10
Severity: MEDIUM
Category: data_classification

Context:

• Pattern: b56e18d47c72ab683b10814fe9495694 is hardcoded as a fallback project ID in three files touched by this PR. Commented as "public projectId only to use on localhost."
• Risk: Functional credential in public source code; normalizes poor credential hygiene in developer-facing docs; any developer copying the snippet gets a shared key silently.
• Impact: Pre-existing; not introduced by this PR. But these files were modified, making it worth noting.

Recommendation: Replace the hardcoded fallback with "YOUR_PROJECT_ID" so omitting the env variable produces a clear error rather than silently using a shared key.

---

Issue 4: PostHog analytics key hardcoded in docs.json (pre-existing)

ID: dcl-docs-json-hardcoded-analytics-key-e2f8
File: docs.json:16
Severity: LOW
Category: data_classification

Context:

• Pattern: phc_8DvuGoAsaF1d8p51zQsrA6PY7KFtbBxfMfl9sgOeS63 hardcoded under integrations.posthog.apiKey.
• Risk: PostHog phc_ keys are client-side write-only ingestion keys and are by design public-facing, so this is low risk in practice. However, it creates a permanent git history record and removes the ability to rotate without rewriting history.
• Impact: Pre-existing; not introduced by this PR.

Recommendation: If Mintlify supports build-time env injection for this field, move it there. If not, explicitly document and accept the risk — PostHog project keys are designed to be public.