maintain-splash-pages

Build a consistent GitHub Pages splash page by scaffolding an Astro-based directory that aligns with Lossless visual conventions and surfaces changelog content. This enforces package isolation to prevent accidentally publishing splash files to JSR or npm public registries.

Add static site search to an Astro splash page by integrating Pagefind, which provides built-in search and sort controls out of the box. This allows users to query and navigate repository documentation without requiring a backend server.

GitHub Pages deployments fail for monorepo splash pages when package isolation is not enforced, causing registry publishing conflicts. Troubleshoot by converting legacy app sites to canonical splash directories and verifying your Astro build output configuration.

The splash page pattern supports single-project, pseudomonorepo, and package-publishing repository variants. It codifies validated reference implementations to ensure consistent public-facing pages across different Lossless Group repository structures.

The best way to maintain repo-level splash pages is using a convention-aligned Astro build with a lenient content schema. This surfaces context-v entries and changelogs while preventing the failure mode of stale, unmaintained project documentation.