Starlight Docs Platform

This note records the Astro/Starlight docs-platform strategy for voiage.

Baseline decision

• Starlight is the authoritative docs-site platform
• Astro 7.1.3 and Starlight 0.41.4 are pinned exactly for reproducible builds
• The default search path should stay on Pagefind unless a later decision justifies a different provider

Active plugins

• astro-polyglot — commit-pinned, language-native API extraction. The initial production lane generates Python API pages with Griffe. Rust, R, Julia, and Mojo extraction remain gated by their native toolchain and conformance evidence.
• starlight-links-validator — broken-link validation during the site build
• starlight-llms-txt — deterministic llms.txt generation

astro-polyglot is consumed from the pinned .repo-tools/astro-polyglot submodule until a reviewed npm release with provenance exists. The documentation workflows build that exact source before running Astro.

Candidate plugins

These are useful if the eventual Starlight site needs the corresponding UX:

• starlight-versions
• starlight-image-zoom
• starlight-heading-badges
• starlight-sidebar-topics
• starlight-utils

Content boundary

The Astro/Starlight site must preserve:

• the current docs content hierarchy
• version-aware navigation
• link validation
• docs build and content smoke checks

The platform decision is complete; future work should evolve the site without introducing a second documentation build system.