Repository navigation
feat: root-base deployment for developers.steem.io origin - #59
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
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.
Repoints the site at its production origin ahead of the developers.steem.io
cutover:
developers.steem.io domain root (CloudFront in front of these GitHub Pages).
VITEPRESS_BASE remains available for sub-path previews.
og:url, canonical and og:image all follow.
all https://developers.steem.io/...; page assets resolve from /assets/;
browser-verified at the domain root (pages, sidebar, live treasury component).
Known transitional effect: after merge, steemit.github.io/steem-docs/* serves
404 until the CloudFront origin path cutover (infrastructure ticket) - that
sub-path was never a public entry point; developers.steem.io keeps serving the
old devportal content throughout, so the cutover itself is zero-downtime.