Remove unused legacy website assets - #39
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 repository still shipped 111 MB of unused imagery from an unrelated legacy physics-lab template, obsolete fonts, superseded headshots, and editor settings tied to a former contributor's machine. This removes those files, ignores future
.vscodestate, and leaves every asset referenced by the current site intact.The production export shrinks by roughly 111 MB. No public content or routes change.
Validation:
npm run checkpassed 30 JavaScript tests, 41 Python tests, content and maintenance validation, a production build, and checks of 106 exported pages and their local links/assets.The requested
bdata.uw.educutover is tracked separately in #38 because UW currently serves a 301 redirect from128.208.3.117; the UW DNS/web record must be changed before GitHub Pages can safely use the custom domain.