Repository navigation
chore: rename the site to AWS Connectivity (base path /aws-connectivity/) - #17
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Prepares the repo for
gh repo rename aws-connectivity. GitHub Pages project sites do not redirect after a rename, so the build has to move with it.base, the PlaywrightbaseURL/webServer URL and the dev URL in the READMEs:/on-ramp/→/aws-connectivity/0-draft/on-ramp→0-draft/aws-connectivitylocalStoragekeys for language and theme:on-ramp:*→aws-connectivity:*(a saved preference resets once)OnRampLinkin the deep dive is nowHomeLink, matching its file"Plan your on-ramp" in the planner keeps the word, since it means the road, not the site.
Merge order: rename the repo first, then merge this so the first deploy under the new name already uses the new base path.
Verification (local)
npm run check: typecheck, ESLint, Prettier, markdownlint, 244 tests, build — pass/aws-connectivity/and/aws-connectivity/direct-connect/; checked desktop and 360px phone in a browser