Migrate the website to Astro and prepare Cloudflare documentation cutover - #7
Merged
Conversation
zayenz
marked this pull request as ready for review
September 5, 2026 12:56
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.
Move the active Gecode website from Jekyll to Astro while keeping GitHub Pages as the origin and serving versioned documentation through Cloudflare Workers and private R2. The users archive gains browsing and search while preserving its historical URLs and fragment targets.
Pages deployment stays manual during the cutover. Worker deployments use separate staging, canary and production environments; production is restricted to reviewed main/release website refs. The documentation Worker handles directory redirects and PDF range validators, and historical publication refuses changes to completed versions.
Validation: staging Worker deployment and HTTP smoke checks passed in https://github.com/Gecode/gecode.github.io/actions/runs/33964652752. Local website quality checks, archive search/mobile checks and the classic rollback build passed. This PR runs the complete website checks from a clean GitHub checkout, including internal links and Lighthouse. Generated documentation is excluded from the Pages artifact.
The runbook records the documentation canary, production documentation soak, later Astro deployment and rollback sequence. Gecode/MPG release publication remains separate follow-up work.