Publish current site and bilingual books after CI - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The public Pages site still showed the pre-restructure installation, and generated books had not been rebuilt. CI now validates and builds both English and Spanish PDF/EPUB editions with MkDocs, makes the downloads discoverable from the site and READMEs, and deploys the site only after every main CI gate succeeds. Superseded main runs skip deployment so an older build cannot roll the site back.
The release workflow uses the same build action to attach books, checksums and their source commit record to future releases. Remaining separate-component installation prose in the manuscripts is corrected. The print stylesheet now wraps long type names inside tables, and a PDF content-stream check rejects off-page text in both full PDFs. The check rejects the original Linux artifacts and passes all 1,105 pages of the corrected local builds. Generated files stay outside Git; Pages uses GitHub Actions instead of the legacy gh-pages branch.
Validation: strict MkDocs build, both PDF/EPUB builds, 17 book pipeline tests (including partially and wholly off-page text fixtures), all 588 PHP listings with provenance, 44 documentation/release/navigation tests (398 assertions), Bash syntax and Actionlint workflow validation. Full PHP matrix and browser checks run on this PR. Pages repository/environment configuration and a live download/hash check follow the green merge.