fix(whitepapers): redirects for PDFs #1520
Draft
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.
Closes #1518. We had similar redirects around 2-3 months ago, before their overhaul, but they didn't work then.
So, PDF redirects work locally, but not in the staging preview. The workaround could (probably) be to make symbolic links from the root. UPD: Nope, symbolic links do not fix this.
In theory, we can do the inverse: place real PDFs in the root and symbolically link to them from
/resources/pdfs/.... But that might break other places which expect files in theresourcesdirectory. Let's just report that to Mintlify if we didn't do it yet.