Port wiki redirects from old Gatsby site to Next.js - #19
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
essentialsx-website | 87f7c6d | Jul 22 2026, 09:56 PM |
JRoy
marked this pull request as ready for review
July 22, 2026 22:02
mdcfe
approved these changes
Jul 23, 2026
JRoy
approved these changes
Jul 27, 2026
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.
The old Gatsby site handled short/unprefixed wiki paths (e.g.
/Home,/BannerMeta.html) via a custom plugin. These redirects were not carried over to the new Next.js site.Changes
next.config.tscovering all paths from the oldwiki-redirectsplugin/Home→/wiki/Home.html→/wiki/introductionbecomes/Home→/wiki/introduction)/Common-Issues,/Common-Issues.html,/help,/help.html→/wiki/faq(closest equivalent in new site)/Module-Breakdown#essentialsx-chat) are intentionally omitted — hash fragments are never sent to the server and cannot be handled via server-side redirects