Repository navigation
Conversation
Replace keeping the same URL on a platform switch with a shared map of topics that exist on several platforms (src/data/platform-topic-map.json). createDocsSite loads it and exposes it as `topicMap` on the site-meta virtual module. DocsSubHeader resolves each platform link at build time: a topic in the map goes to that platform's `base` + slug, every other page goes to the platform's getting started page. Nothing is fetched. Needs igniteui-astro-components with `topicMap` support (IgniteUI/igniteui-astro-components#132). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cross-platform topic map: report
Proposed
1. Method1.1 Real slug setsA page's slug is its Astro content-collection id. Every step that decides which pages exist was re-implemented and run over sources extracted from git objects ( xplat (React, Web Components, Blazor) —
Angular — the build runs
Content collection —
Cross-check:
1.2 Pairing
2. Slug counts
Pages that exist only because of generation (en):
jp vs en:
3. Relation families
3.1 Identical slugs (163)They split by platforms covered: 113 entries cover A R W B, 21 cover A R W, and 29 cover R W B only.
3.2 Non-obvious relations
3.3 Grid rule coverage
3.4 Identical slugs deliberately not used (the validator's 4 coverage warnings)
4. Needs review (8, not in the map)
Rejected look-alikes (different subjects;
5. No counterpart (confident)Angular (106 unmapped):
Other sites:
6. jp gaps
7. Suspected problems
8. FilesThe proposed map is 🤖 Generated with Claude Code |
Fill src/data/platform-topic-map.json with 343 topics, built against vnext 697e3b5: 163 that share a slug on every platform they exist on and 180 whose slugs differ (mostly Angular vs the xplat platforms). Only pairings confirmed on page content are included; the 8 uncertain ones and the reasoning are in the PR comment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No description provided.