Add static contextual internal links across content pages#719
Conversation
|
Warning Review limit reached
More reviews will be available in 20 minutes and 7 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (300)
Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|



Description de la requete
This replaces the previous generic cross-link component approach with static, page-specific text inclusions. The generated site now has plain Markdown/MDX or static Astro copy placed directly in the source page content. No shared runtime cross-link component remains.
Each inclusion is written as visible text for that page and links to five related internal pages. The target pages are selected by the page topic: live updates, channels, rollbacks, CI/CD, security, auth, store review, plugins/native bridge, payments, analytics, media/UI, storage/files, API/webapp, and enterprise migration.
Before / after measurement
Before: 0 static page-specific internal-link inclusions from this PR.
After: 4,475 static internal links across 895 rendered pages:
Mirrored plugin docs were also synced under
src/content/docs/docs/plugins/**so the docs mirror check remains byte-for-byte aligned.Link coverage
Every edited page has a
Keep going from ...text inclusion with exactly five internal links. Examples:/blog/secure-token-storage-best-practices-for-mobile-developers/links to encryption, compliance, security scanner, security, and trust pages./blog/2-way-communication-in-capacitor-apps/links to the plugin directory, plugin docs, adding plugins docs, Ionic enterprise plugin alternatives, and native builds./docs/live-updates/channels/links to public API channels, webapp channels, beta testing, version targeting, and the staging-with-channels article./plugins/capacitor-live-activities/links to Live Activities docs, getting started docs, Video Player plugin, Video Player docs, and Native Navigation plugin./live-update/links to channels, rollbacks, update behavior, version targeting, and native builds.Validation
bunx prettier --writeon changed Astro/templatesbun run checkbun run buildNotes: local checks pass. The only browser issue seen during preview was the existing docs preview
/favicon.svg404. The web check still reports the existing hint inapps/web/src/worker/readme-banner.ts.