website sunset and polkadot.com redirects #352
Conversation
This file contains 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
✅ Deploy Preview for substrate-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
nprt
changed the title
RemyLeBerre
reviewed
Jan 20, 2025
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.
The larger effort of getting substrate.io sunset involves the redirects being properly set and implemented. The main reason behind this is to preserve SEO as much as possible during the migration effort. For this reason, we should place redirects as closely as possible to the newly added pages.
This PR addresses the reasons mentioned above - placing redirects for substrate.io into polkadot.com/platform/sdk.
Note: The accompanying PR - polkadot-developers/substrate-docs#2185.
Note: More information can be found in the private repository here.