reversa-docs-publisher

To generate an offline-ready documentation mini-site, you need a final aggregation stage that integrates generated HTML pages into a consistent index with embedded data. This approach forbids local fetch usage, embedding all required data via window.RV_DATA so pages work reliably offline.

Validating relative links and bundling assets for static site generation requires bundling pinned vendor libraries into assets/vendor. The pipeline performs link checks, runs a smoke test, and writes final telemetry plus deterministic seal assets to ensure file:// compatibility.

Turning scattered HTML outputs into a navigable offline-first mini-site involves injecting a consistent header mini-seal and navigation links across all generated pages. This creates deterministic identity and navigation, ensuring a coherent documentation site without broken links or missing assets.

Static site generation for offline documentation requires upstream generators to have already produced HTML and auxiliary discovery outputs. This final aggregation stage applies to documentation pipelines that need to integrate these scattered outputs into a single offline-ready index.

Offline documentation mini-sites break when opened via file:// because they attempt local fetch usage. Forbidding local fetch and embedding all required data directly into the pages ensures file:// compatibility without missing assets or broken links.