[Hristo313]

Closes #920

Also updated the samples:
Angular -> IgniteUI/igniteui-angular-samples#4064
React -> IgniteUI/igniteui-react-examples#1136
WC -> IgniteUI/igniteui-wc-examples#1305
Blazor -> IgniteUI/igniteui-blazor-examples#1345

Rearranges the left navigation and ports the RTL topic to all web platforms.

Navigation (xplat and Angular TOCs, EN and JP)

• Accessibility Compliance and RTL Support move from Interactivity to General, and the empty Interactivity header is removed. The file paths and URLs stay the same, so no redirects are needed.
• Styling & Themes moves right after General: AI-Assisted Development → General → Styling & Themes → Grids & Lists → …
• The TOC files were edited by moving lines, not by a JSON round-trip.

RTL topic

• New xplat source at docs/xplat/src/content/en/components/interactivity/right-to-left-support.mdx. It builds for Angular, React, Web Components and Blazor (platformType: web-only).
• Rewritten on the current topic template, with the facts checked against the component source:
  • Enable RTL with dir="rtl" on body.
  • Switch the direction at runtime.
  • Apply RTL to part of a page.
  • Mirror directional icons.
  • Known limitations per platform: the grids and the Calendar don't mirror the arrow keys; in Angular the Tree doesn't either; in Web Components, React and Blazor the Carousel and the Navigation Drawer follow only dir on body or on the component.
• Fixes in the old content:
  • The wrong title and description.
  • The removed igx-core($direction: rtl) Sass, moved to Troubleshooting with the 13.2.0 change.
  • The "runtime changes are not detected" note: true only before 22.0.0.
• The Angular copy is removed and listed with the generated files in docs/angular/src/content/{en,jp}/.gitignore.

Samples

The topic references the samples by their new paths. The sample PRs follow separately:

• Angular: /scheduling/calendar-rtl, renamed from calendar-rtl-sample.
• React, Web Components, Blazor: /scheduling/calendar/rtl.

JP

• The JP TOCs get the same moves. The JP xplat TOC entry for RTL is left to jp-sync, which adds it together with the translation; a hand-added entry fails the relative-links check while the JP file doesn't exist.
• jp-sync removes the JP Angular RTL copy and adds the JP xplat translation in two PRs. Merge them together, or JP Angular is left without the RTL page in between.

Checks run locally

• Builds with DOCS_TOC_STRICT=true: angular:build, and xplat:build for React, Web Components, Blazor, Angular and WinUI.
• check-relative-links:ci and check-mdx-links:broken for Angular, React, Web Components and Blazor.
• check:llms-metadata, cspell and markdownlint.

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
• link to other topics using ./page.mdx or ../relative/path.mdx (.mdx extension required)
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check if links function by running the check-api/mdx npm commands
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo
• add or update meaningful llms.description metadata and run npm run check:llms-metadata

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)

🤖 Generated with Claude Code