deploy-docs

To validate an Eleventy build for GitHub Pages, run npm ci and npx @11ty/eleventy to generate the _site output, then verify critical assets like index.html, sitemap.xml, and css/style.css exist to guarantee site integrity before deployment.

Critical files in your Eleventy docs site output include index.html, agents.html, skills.html, changelog.html, getting-started.html, 404.html, css/style.css, CNAME, and sitemap.xml, ensuring complete site integrity for deployment.

This docs deployment automation works with GitHub Pages setups using Eleventy to render documentation, executing build validation and preparing reproducible deployment artifacts for your existing repository configuration.

Your Eleventy documentation build fails site integrity checks when essential generated pages or assets, such as index.html, 404.html, or CNAME, are missing from the _site output directory after the build process completes.

The best way to automate documentation deployment for Eleventy projects is using a repeatable workflow that validates the build, checks for required output assets, and prepares GitHub Pages-ready artifacts in one consistent run.

Yes, you can use this to prepare GitHub Pages deployment artifacts without manual checks, as it automatically verifies the presence of critical pages and assets like sitemap.xml and CNAME after executing the Eleventy build.