Merged
Conversation
kescobo
approved these changes
Jan 27, 2026
Member
There was a problem hiding this comment.
Are these removals intended in this PR? seems like a separate thing (which is fine - just want to confirm).
Collaborator
Author
There was a problem hiding this comment.
Haha, I just noticed that they were there. It is a separate thing. I can try to separate out the PRs more cleanly in the future 😂 Can also leave the hamburger in if preferred. 🍔
Member
There was a problem hiding this comment.
Same question here - logo changes intended here?
Collaborator
Author
There was a problem hiding this comment.
Yes, not directly related to the deployment link updates. I included everything in 1 PR since they are all small changes. But I'll make multiple smaller PR's in the future.
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
2 participants
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.
Bug: The links in the newly deployed website are correct (double checked for spelling errors!) but still leading to 404 errors.
Explanation: After some research, the cause was determined to be Vitepress changing the URL's after deployment. The URL's for the bioJulia packages start with
https://biojulia.dev/, just like the Biojulia site. When the Biojulia site was deployed at/dev/, the router was mangling the URLs. Vitepress uses client-side routing.Fix: All 35 biojulia.dev links now have
rel="external". This tells VitePress to treat them as external links and bypass client-side routing. Let's re-deploy and see if this solves the issue!