feat(astro)!: cut over production site to the astro build (develop → main release)#36
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
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.
Release: Astro migration cutover
Replaces the hand-authored static site on
mainwith the Astro-generatedbuild that has been developed on
develop. After this merges, themain-only deploy workflow ships the Astro site to GitHub Pages — this is
the production cutover.
What ships
generates
docs/.Divergence note
main's recent #27 (analytics lesson-id) and #31 (footer note) were hot-fixesto the old hand-authored files, which no longer exist here. Their equivalents
already live in the Astro source (#25 analytics lesson_id, #30 footer note), so
the
-s oursback-merge intentionally supersedes them — nothing is lost.Verification
pnpm build— 98 pages, greennode scripts/validate-content.cjs— passednode scripts/check-broken-links.cjs— no broken internal links9d64013);origin/mainisnow an ancestor, so this PR is conflict-free.