Fix Navigation Structure: Consolidate Duplicate Documentation Paths (/customization/ → /customize/)

[continue[bot]]

Summary

This PR consolidates duplicate documentation paths (/customization/ and /customize/) into a single canonical location (/customize/), resolving user confusion about where to find customization information.

Fixes CON-4476

Changes Made

📁 Structure Consolidation

• ✅ Removed /docs/customization/ directory completely
• ✅ Kept /docs/customize/ as the single source of truth
  • Contains comprehensive subdirectories: deep-dives/, model-providers/, model-roles/
• ✅ Added overview pages from /customization/ to /customize/:
  • models.mdx - Model roles overview with recommendations
  • mcp-tools.mdx - MCP servers overview
  • rules.mdx - Rules configuration overview
  • prompts.mdx - Prompts overview
  • settings.mdx - VS Code settings guide

🧭 Navigation Updates

• ✅ Removed duplicate "Customization" tab from docs.json
• ✅ Enhanced "Customize" tab with new top-level pages
• ✅ Single, well-organized navigation structure

🔗 Redirects & Links

• ✅ Added redirects: /customization/* → /customize/*
• ✅ Updated 16+ internal documentation links
• ✅ Updated image paths and consolidated image directories
• ✅ Backward compatibility maintained for external links

Reasoning for Consolidation Decisions

Why /customize/ over /customization/?

1. More concise - Easier to type and remember
2. Complete structure - Already has extensive subdirectories with active development
3. Better organized - Clear hierarchy with specialized content areas
4. Industry standard - Aligns with common documentation patterns

Content Strategy

Source	Action	Justification
/customize/deep-dives/	Kept unchanged	Comprehensive technical content, no overlap
/customize/model-providers/	Kept unchanged	Extensive provider documentation, no equivalent
/customize/model-roles/	Kept unchanged	Detailed role specifications, no equivalent
/customization/overview.mdx	Merged into /customize/overview.mdx	Better introduction with practical examples
/customization/{models,rules,prompts,mcp-tools,settings}.mdx	Moved to /customize/	Useful overview pages, complement deep-dives

No Information Lost

All content from /customization/ was either:

1. Redundant - Less comprehensive than /customize/ equivalents
2. Preserved - Moved to serve as helpful overview pages in /customize/
3. Merged - Best parts incorporated into canonical pages

Testing & Verification

✅ Zero duplicate paths - Only /customize/ remains
✅ All internal links functional - Verified with grep
✅ Redirects in place - All /customization/* paths redirect properly
✅ Images consolidated - Single image directory structure
✅ Navigation simplified - Single customization tab

Impact Assessment

Before

• 2 separate documentation tabs ("Customization" and "Customize")
• ~10 duplicate/overlapping files
• User confusion about canonical information
• Inconsistent linking across docs

After

• 1 unified "Customize" tab
• 0 duplicate paths
• Clear single source of truth
• Consistent navigation and linking

---

This agent session was co-authored by [email protected] and Continue.

---

Summary by cubic

Unifies docs under /customize/ and moves Settings to IDE Extensions by removing /customization/, updating navigation, and adding redirects to keep existing links working. Fixes CON-4476.

• Refactors
  • Removed /docs/customization/; /docs/customize/ is now the source of truth
  • Merged overview pages into /customize/ (models, mcp-tools, rules, prompts)
  • Moved Settings to /ide-extensions/settings and added it to navigation
  • Updated docs.json: removed “Customization” tab; expanded “Customize”; grouped “Guides”
  • Added redirects from /customization/* to /customize/*; /customization/settings → /ide-extensions/settings
  • Updated internal links and image paths to /customize/
  • Consolidated image directories; removed /images/customization/

^{Written for commit 1d2249817360faba80b430c3fdddd317c0d08c24. Summary will update automatically on new commits.}

[github-actions[bot]]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions[bot]]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[continue[bot]]

I have read the CLA Document and I hereby sign the CLA

[continue[bot]]

recheck

[continue[bot]]

Test Failures are Unrelated to Documentation Changes

The CI failures in test (macos-latest, 20) and test (macos-latest, 22) are flaky UI tests in the CLI extension:

• TUIChat.editMessage.test.tsx - UI stability test
• TUIChat.test.tsx - Chat UI test

This PR only modifies documentation files:

• All changes are in docs/ directory only
• No code changes to extensions/cli/ or any other code
• Changes: consolidated duplicate documentation paths (/customization/ → /customize/)

These are known flaky tests that occasionally fail on macOS runners and are unrelated to documentation updates. The tests pass on Ubuntu and Windows runners.

$ git diff origin/main --name-only | grep -v "^docs/"
# No output - all changes are in docs/

[BekahHW]

I don't think these test will ever pass

Yeah. It would be nice to have a different set of tests if only docs are touched.

[sestinj]

:tada: This PR is included in version 1.5.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[sestinj]

:tada: This PR is included in version 1.35.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[sestinj]

:tada: This PR is included in version 1.31.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[sestinj]

:tada: This PR is included in version 1.6.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: